Review every change before it merges
Open a pull request from a branch, review its commits and files, ask for approvals, then squash, fast-forward or merge.
Open a pull request
Choose the branches and give it a title and a description in Markdown. Pull requests are numbered with the repository's issues.
Review the changes
Its commits and the files changed, as unified or split diffs, with renamed files shown as renames. Comment on any line, and reply in its thread.
Reviewers and approvals
Ask members to review, and each gets an email. Anyone who can write the repository can approve, except the author, and branch rules can require approvals and code owners.
Merge
Squash, fast-forward or a three-way merge, whichever the branches allow. If the branch moved since you opened the page, the merge stops rather than take commits you haven't seen.
And on every pull request
Pipeline checks
The latest commit's pipeline runs, each opening its jobs and logs.
Preview deployments
The previews from Cloud for the branch, beside its checks.
Closes its issues
Fixes #12 in the title, description or merge message closes the issue when it merges.
Email to the right people
Reviewers when they're asked, the author on an approval, and everyone involved on the merge.
Ship your team's code from Git
Complete and Enterprise include it, with Pipelines, Cloud and the rest of your workplace.