Skip to content
GitHub Copilot is now available for free. Learn more
Code Review

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.

Get startedContact sales
The image shows a GitHub interface for opening a pull request. It features dropdown menus for selecting base and compare branches, a green checkmark indicating automatic merge capability, a text box for comments, and formatting options.

Every change starts with a pull request.

Learn pull request fundamentals
  • 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

This image visually represents changes made to a stylesheet file, highlighting how the layout or design of a web page might be altered through these CSS adjustments.

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.

Learn more

History

Screenshot of two commits added, and the changes were approved.

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.

Learn more

Blame

Image showing a file history showing four version entries with names and timestamps: 'First draft' and 'delete old pricing,' modified over the past few months.

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.

Learn more

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.

The image shows a section of a user interface. At the top, there is a list with three items: "Line 10: Layouts" with a minus sign in red, "Line 11: Grid system" with a plus sign in green, and "Line 12: Layout are built on a 12 column grids." Below this list, there is a comment from the user "rajqflow" made 1 day ago that says, "Good cal, this is more specific!" The comment has received 5 thumbs-up likes and 2 heart reactions.

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.

The image shows a user interface for requesting a review. At the top, there is a text box with the placeholder "Request a review" and an input field below it containing the letter "o". Underneath the input field, there are two user suggestions: "kharyrizen Raymonda Khouri" with an avatar of a person, and "hankzolo Hank Zoeng" with an avatar of another person.

Reviews

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

The image displays a notification message. The notification features a red circle with a white 'X' icon and the title "Review required." Below the title, it states, "At least one approve review is required by reviewers to write access. Learn more." Additionally, there is an avatar of a person with the username "khayrizen" and text indicating that this user was requested for review.

You can’t always avoid conflict. Merge pull requests faster by resolving simple merge conflicts on GitHub—no command line necessary.

Learn more
Alert indicating a branch conflict with files that need to be resolved before merging.

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

Give collaborators as much access as they need through your repository settings. You can extend access to a few teams and select which ones can read or write to your files. The options you have for permissions depend on your plan.

See plan options

Protected branches

Protected Branches help you maintain the integrity of your code. Limit who can push to a branch, and disable force pushes to specific branches. Then scale your policies with the Protected Branches API.

Learn more

Required status checks

Create required status checks to add an extra layer of error prevention on branches. Use the Status API to enforce checks and disable the merge button until they pass. To err is human; to automate, divine!

Status API doc

Every change starts with a pull request.

Get started