Every change starts with a pull request.
Write better code
On GitHub, lightweight code review tools are built into every pull request. Your team can create review processes that improve the quality of your code and fit neatly into your workflow.
Every change starts with a pull request.

- Start a new feature or propose a change to existing code with a pull request—a base for your team to coordinate details and refine your changes.
- Pull requests are fundamental to how teams review and improve code on GitHub. Evolve projects, propose new features, and discuss implementation details before changing your source code.
See every update
and act on it, in-situ

Diffs
Preview changes in context with your code to see what is being proposed. Side-by-side Diffs highlight added, edited, and deleted code right next to the original file, so you can easily spot changes.

History
Browse commits, comments, and references related to your pull request in a timeline-style interface. Your pull request will also highlight what’s changed since you last checked.

Blame
See what a file looked like before a particular change. With blame view, you can see how any portion of your file has evolved over time without viewing the file’s full history.
Discuss code
within your code
Comments
On GitHub, conversations happen alongside your code. Leave detailed comments on code syntax and ask questions about structure inline.

Review requests
If you’re on the other side of the code, requesting peer reviews is easy. Add users to your pull request, and they’ll receive a notification letting them know you need their feedback.

Reviews
Save your teammates a few notifications. Bundle your comments into one cohesive review, then specify whether comments are required changes or just suggestions.

Merge the highest quality code
Reviews can improve your code, but mistakes happen. Limit human error and ensure only high quality code gets merged with detailed permissions and status checks.
Fast, relevant results
Set a minimum number of approving reviews, whether Copilot or human, before any pull request can merge.
Protected branches
Control how code gets merged. Restrict who can push, require linear history, and prevent force pushes.
Required status checks
Ensure CI passes, tests are green, and automated gates clear before the merge button is enabled.