Pull requests and code review
Comment on any line, suggest exact changes, require approvals and passing checks, and merge through a queue that tests each pull request against the latest main.
- Suggested changes
- Write the change you want in a review comment. The author can apply one suggestion or a batch of them as a single commit.
- Branch protection
- Require approvals, passing checks and code owner reviews before a pull request can merge.
- Merge queue
- Queued pull requests are tested in order against the latest main and merge automatically when their checks pass.
- Conflict resolution
- Fix merge conflicts in a side-by-side editor in the browser, without checking out the branch.
Review history on one timeline
Approvals, change requests, dismissals and re-requests appear on the pull request timeline alongside commits, deployments and linked issues. Reviewers can see which commit they last reviewed.
Merge, squash or rebase
Choose which merge methods each repository allows. With auto-merge on, gitfor merges as soon as reviews and checks pass, and closes the issues your commits reference.
Try it on your own code
Create an account and import a repository with its full history, or run your own instance.