Skip to content

Latest commit

 

History

History
59 lines (34 loc) · 2.69 KB

File metadata and controls

59 lines (34 loc) · 2.69 KB

🔨 Hands-on: Code reviews

In this hands-on lab you will learn how to perform code reviews. The exercise consists of the following parts:

Getting ready for review

  • Got to your own pull request and indicate that you are Ready for review:

image

This will change the status of the PR from draft to ready. As we require a review, merging is blocked.

Enable auto-merge

  • Enable auto-merge for the PR. Note the different merge types - we'll learn later what they mean. Just leave the default.

image

  • The merge commit needs a commit message - just leave the default and Confirm auto-merge:

image

Performing the review

Note
Wait until your partner from #1 is ready. You'll perform the review for their PR.

  • Go to the PR of your partner from #1 (you should have received a request for review after the status of the pul request was changed)
  • Navigate to Files changed and add a comment
  • Select Start a review this time.

image

  • Add multiple comments to your review and note that they are pending:

image

  • When you are ready Finish your review. Only approve will merge the PR - all other results will still block the merge.
  • Submit the review:

image

  • Note that the status automatically changes to Merged and the HEAD branch gets deleted (that is a setting in the repo).
  • Note that you can revert the changes and restore the deleted branch:

image

Wait until GitHub pages is refreshed and see the results...

Summary

In this lab you've learned how to perform code reviews and use auto-merge. You can now go back to Collaborate on code.