⇦ Back to: Clean up | ⇧ Overview | ⇨ Next: Merge Conflict

How to update your Pull Request

Reasons you might want to update a pull request include:

• Addressing comments and requested changes
• The main branch has changed

These two cases are dealt with differently.

Addressing comments and requested changes

Wait until you have the amount of feedback you need.

• If your PR is approved by everyone, congratulations!

• If not, and once you’ve got the feedback you want, then

  • 🛠 fix any shortcomings on the same branch, making new commits, and then
  • push the updated branch using git push when you’re done.

• Important: Ensure you re-request the review from your reviewers once you’re finished with the updates.

  

Merging changes from main

If another PR is merged into main before yours, you can update your branch.

If someone else has changed how a piece of code works, it’s good to check that your changes still work with the other person’s update, or whether you need to make new changes yourself.

Using GitHub

If there are no conflicts detected, then the pull request will show this at the bottom:

If there are conflicts, it will offer you the option to resolve the merge conflicts (covered in the next section).

<aside> 💡 Repository Admins can go into the repository Settings and activate the option “Always suggest updating pull request branches”, to show an “update branch” button at the bottom of the pull-request, for cases when “main” has been updated.

</aside>