Skip to content

TutorTask610_Fixes_on_book_programming_with_ai#611

Open
andresryes wants to merge 1 commit intomasterfrom
TutorTask610_Fixes_on_book_programming_with_ai
Open

TutorTask610_Fixes_on_book_programming_with_ai#611
andresryes wants to merge 1 commit intomasterfrom
TutorTask610_Fixes_on_book_programming_with_ai

Conversation

@andresryes
Copy link
Collaborator

Checklist

Post this checklist in a PR and check the boxes when the PR meets the
requirements

  • The branch is named following the format
    RelatedIssueTag_Normalized_issue_title
  • Commit messages are short and informative
    • Ideally, they follow the format
      RelatedIssueTag: High-level commit description
    • E.g., HelpersTask123: Add example
    • They do not mention the name of the file that has been changed by the commit
  • The title of the PR matches the name of the branch
  • The starting post of the PR briefly describes the content of the PR on a
    high level
  • The issue related to the PR is mentioned in the starting post of the PR
  • The PR is not linked to any issues under the Development section
  • At least one reviewer is assigned under Reviewers
  • The PR author is listed under Assignees
  • All the checks performed by GitHub Actions pass
    • If they do not and it can't be fixed, explain why in a comment
    • E.g., "The fast tests failure is also present in master and is unrelated
      to this PR"
  • The branch is up to date with the master branch
  • There are no conflicts with the master branch
  • There are no files checked in by mistake (such as tmp and log files)
  • All checked in files are checked and formatted by Linter in the latest
    commit
  • No files larger than 500 KB are checked in
  • Screenshots are not used in PR posts to describe the situation or report
    an error (if needed, copy-and-paste is used instead)
  • Label PR_for_reviewers is present if a review is requested
  • Fixes addressing a review comment are applied everywhere, not just where
    the reviewer pointed out the issue
  • After addressing review comments, all corresponding conversations are
    marked as resolved
  • After all review comments are resolved, re-request review button is used
    to request another round of review

@andresryes andresryes requested a review from Shaunak01 July 31, 2025 18:07
@andresryes andresryes self-assigned this Jul 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant