learn-gw-review

To handle code review feedback on a GitHub pull request, you triage comments into blocking fixes, questions, and nitpicks. Then you revise the code, commit the intended files, push the changes, and perform a squash merge followed by branch cleanup.

Triage for a pull request involves separating blocking fixes that must change immediately from reviewer questions and minor nitpicks. This categorization ensures you address critical code review issues first before proceeding to revisions and merges.

To safely revise code after a pull request review, update your implementation, explain your reasoning, commit only the intended files, and push the corrected changes. This targeted workflow ensures you address feedback without unintended modifications.

To complete a squash merge and clean up a git branch, perform the merge via GitHub or git commands, delete the local and remote branches to clean up, and call complete_work to accurately record the finished project progress.

Yes, you can mark ProjSight task completion after merging a pull request by calling complete_work at the end of your workflow. This records the finished work accurately once your squash merge and branch cleanup are fully complete.

Yes, resolving review comments and completing the merge workflow requires using gh, git, and complete_work. These tools facilitate applying targeted code changes, pushing corrections, performing squash merges, and recording task completion.