Article version: Enterprise Server 2.15

This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2019-10-16. 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. For help with the upgrade, contact GitHub Enterprise support.

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 master branch only contains finished and approved work.

Anyone with read permissions to a repository can create a pull request, but you must have write permissions to create a branch. If you want to create a new branch for your pull request and don't have write permissions to the repository, you can fork the repository first. For more information, see "Creating a pull request from a fork" and "About forks."

You can specify which branch you'd like to merge your changes into when you create your pull request. Pull requests can only be opened between two branches that are different.

You can close corresponding issues using a keyword in your pull request or commit message. For more information, see "Closing issues using keywords."

Changing the branch range and destination repository

By default, pull requests are based on the parent repository's default branch.

If the default parent repository isn't correct, you can change both the parent repository and the branch with the drop-down lists. You can also swap your head and base branches with the drop-down lists to establish diffs between reference points. References here must be branch names in your GitHub repository.

Pull Request editing branches

When thinking about branches, remember that the base branch is where changes should be applied, the head branch contains what you would like to be applied.

When you change the base repository, you also change notifications for the pull request. Everyone that can push to the base repository will receive an email notification and see the new pull request in their dashboard the next time they sign in.

When you change any of the information in the branch range, the Commit and Files changed preview areas will update to show your new range.


  • Using the compare view, you can set up comparisons across any timeframe. For more information, see "Comparing commits across time."
  • Project maintainers can add a pull request template for a repository. Templates include prompts for information in the body of a pull request. For more information, see "About issue and pull request templates."

Creating the pull request

  1. On GitHub Enterprise, navigate to the main page of the repository.

  2. In the "Branch" menu, choose the branch that contains your commits.

    Branch dropdown menu

  3. To the right of the Branch menu, click New pull request.

    Pull Request button

  4. Use the base branch dropdown menu to select the branch you'd like to merge your changes into, then use the compare branch drop-down menu to choose the topic branch you made your changes in.

    Drop-down menus for choosing the base and compare branches

  5. Type a title and description for your pull request.

    Pull request title and description fields

  6. Click Create pull request.

    Create pull request button

Tip: After you create a pull request, you can ask a specific person to review your proposed changes. For more information, see "Requesting a pull request review."

After your pull request has been reviewed, it can be merged into the repository.

Further reading

Ask a human

Can't find what you're looking for?

Contact us