This version of GitHub Enterprise Server will be discontinued on 2026-03-17. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise Server. For help with the upgrade, contact GitHub Enterprise support.
Pull requests documentation
Learn how to use pull requests to suggest changes to a project, receive suggested changes to your own projects, and address issues in pull requests, such as merge conflicts.
Recommended
About pull requests
Pull requests let you propose, review, and merge code changes.
About collaborative development models
The way you use pull requests depends on the type of development model you use in your project. You can use the fork and pull model or the shared repository model.
Creating a pull request
Create a pull request to propose and collaborate on changes to a repository. These changes are proposed in a branch, which ensures that the default branch only contains finished and approved work.
Articles
About branches
Use a branch to isolate development work without affecting other branches in the repository. Each repository has one default branch, and can have multiple other branches. You can merge a branch into another branch using a pull request.
About collaborative development models
The way you use pull requests depends on the type of development model you use in your project. You can use the fork and pull model or the shared repository model.
About commits
You can save small groups of meaningful changes as commits.
About comparing branches in pull requests
Pull requests display diffs to compare the changes you made in your topic branch against the base branch that you want to merge your changes into.
About forks
A fork is a new repository that shares code and visibility settings with the original "upstream" repository.
About merge conflicts
Merge conflicts happen when you merge branches that have competing commits, and Git needs your help to decide which changes to incorporate in the final merge.
About permissions and visibility of forks
The permissions and visibility of forks depend on whether the upstream repository is public or private, whether it is owned by an organization, and the policies of your enterprise.
About pull request merges
You can merge pull requests by retaining all the commits in a feature branch, squashing all commits into a single commit, or by rebasing individual commits from the head branch onto the base branch.
About pull request reviews
Collaborate on pull requests to improve code quality.
Showing 1-9 of 54