Pull Requests & Code Review
In the previous lesson we learned to connect our local repo to a server (GitHub) and sync with it: clone, push, pull. Now we ask a completely different question — not 'how do I upload code' but 'how does a team let code land safely'. The answer is the Pull Request: a request to merge one branch into
A Pull Request is like saying 'I finished a hotel room — please inspect it before guests come in'. Instead of pushing your work straight into the main line (main), you open a request: 'here's my change, let's talk about it, leave comments, run checks — and only when everything's good, we let it in'.
- Pull Request (PR)
- A request on GitHub to merge one branch into another (usually a feature branch into main). It opens a place for discussion, code review, and automated checks before the change lands.
- Code review
- When a teammate reads your change, leaves comments, and suggests improvements inside the PR — to catch bugs, share knowledge, and keep quality high.
- Approve
- The reviewer's 'looks good to me' mark — a green light saying that, from their side, the PR is fine to merge.
- Automated checks (CI)
- Software that runs by itself on every PR and checks the code (for example, runs the tests). If a check fails, you fix it before merging.
- Merge a PR
- The button that finally brings your branch into main after the review is approved and checks pass. The feature branch is then usually deleted.
