Introduction

---

Example Code

---

• Encountering a “bad” code repository is an opportunity to learn what not to do!

Fixing a Repository Issue

---

• We use branches to contain the change commits we want to submit within a pull request

Submitting a Pull Request

---

• Try to keep pull requests short-lived to avoid them becoming outdated with other branches such as main
• We can request reviewers for a pull request by adding their GitHub account to a list of Reviewers

Reviewing a Pull Request

---

• The key reason to use pull requests is to ensure that code changes are reviewed by other team members before they are merged
• We can elect to approve changes, request changes prior to merging a pull request, or block a merge until requested changes are satisfied
• GitHub doesn’t allow the creator of a pull request to approve it

Merging a Pull Request

---

• Following a merge, pull request branches are deleted in keeping with the short-lived branch philosophy of GitHub