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.

Who can use this feature?

Anyone with read access to a repository can create a pull request. Members of an enterprise with managed users can only propose changes in repositories that are part of their enterprise.

Platform navigation

In this article

If you want to create a new branch for your pull request and do not 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.

Note: To open a pull request in a public repository, you must have write access to the head or the source branch or, for organization-owned repositories, you must be a member of the organization that owns the repository to open a pull request.

You can link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request. For more information, see "Linking a pull request to an issue."

Changing the branch range and destination repository

By default, pull requests are based on the parent repository's default branch. For more information, see "About branches."

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.

Screenshot of a pull request. The dropdown to edit the compare branch is expanded.

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.

Tips:

  • Using the compare view, you can set up comparisons across any timeframe. For more information, see "Comparing commits."
  • 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, navigate to the main page of the repository.

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

    Screenshot of the branch dropdown menu on the main page of a repository.

  3. Above the list of files, in the yellow banner, click Compare & pull request to create a pull request for the associated branch.

    Screenshot of the banner above the list of files.

  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.

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

  6. To create a pull request that is ready for review, click Create Pull Request. To create a draft pull request, use the drop-down and select Create Draft Pull Request, then click Draft Pull Request. If you are the member of an organization, you may need to request access to draft pull requests from an organization owner. See "About pull requests."

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.

To learn more about GitHub CLI, see "About GitHub CLI."

To create a pull request, use the gh pr create subcommand.

gh pr create

To assign a pull request to an individual, use the --assignee or -a flags. You can use @me to self-assign the pull request.

gh pr create --assignee "@octocat"

To specify the branch into which you want the pull request merged, use the --base or -B flags. To specify the branch that contains commits for your pull request, use the --head or -H flags.

gh pr create --base my-base-branch --head my-changed-branch

To include a title and body for the new pull request, use the --title and --body flags.

gh pr create --title "The bug is fixed" --body "Everything works again"

To mark a pull request as a draft, use the --draft flag.

gh pr create --draft

To add a labels or milestones to the new pull request, use the --label and --milestone flags.

gh pr create --label "bug,help wanted" --milestone octocat-milestone

To add the new pull request to a specific project, use the --project flag.

gh pr create --project octocat-project

To assign an individual or team as reviewers, use the --reviewer flag.

gh pr create --reviewer monalisa,hubot  --reviewer myorg/team-name

To create the pull request in your default web browser, use the --web flag.

gh pr create --web

  1. Click Preview Pull Request. GitHub Desktop will open a preview dialog showing the diff of the changes between your current branch and the base branch.

    Screenshot of the "No local changes" view. A button, labeled "Preview Pull Request", is highlighted with an orange outline.

    Screenshot of the "No local changes" view. A button, labeled "Preview Pull Request", is highlighted with an orange outline.

    Alternatively, to go straight to GitHub to create your pull request, select the dropdown icon and click Create Pull Request.

  2. Confirm that the branch in the base: dropdown menu is the branch where you want to merge your changes.

    Screenshot of the "Open a Pull Request" dialog window. A button with a dropdown icon, labeled "base: development", is outlined in orange.

    GitHub Desktop will advise you whether the current branch can be automatically merged into the base branch.

    Screenshot of the "Open a Pull Request" dialog window. A status label stating "Can't automatically merge" is highlighted with an orange outline.

  3. Click Create Pull Request. GitHub Desktop will open your default browser to take you to GitHub.

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

  5. To create a pull request that is ready for review, click Create Pull Request. To create a draft pull request, use the drop-down and select Create Draft Pull Request, then click Draft Pull Request. If you are the member of an organization, you may need to request access to draft pull requests from an organization owner. See "About pull requests."

  1. Once you've committed changes to your local copy of the repository, click the Create Pull Request icon.
    Screenshot of the top of the "Source Control" side bar. The pull request icon is highlighted with a dark orange outline.
  2. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description.
    Screenshot of the "GitHub Pull Request" side bar with a form for creating a pull request, including "Title" and "Description" fields.
  3. Click Create.

For more information on creating pull requests in GitHub Codespaces, see "Using GitHub Codespaces for pull requests."

Making changes to files in your pull request

After you have opened your pull request, you can continue making changes to the files by adding new commits to your head branch.

You can also make changes to files on the GitHub website.

  1. On GitHub, navigate to a pull request in a repository.

  2. On the pull request, click Files changed.

    Screenshot of the tabs for a pull request. The "Files changed" tab is outlined in dark orange.

  3. Scroll down to the file you want to make changes to.

  4. Above the file you want to change, click .

    Screenshot of the options above a file on the "File changed" tab. The "Show options" button is highlighted with an orange rectangle.

  5. In the menu, click Edit file.

  6. Make your changes in the editor and when committing your change, choose to commit directly back to your head branch.

If you are part of the public preview of Copilot Workspace, clicking Edit on a file on the "Files changed" tab will open the file in a Copilot Workspace on GitHub. In a Copilot Workspace, you can still make changes to the file but also make changes to other files in the repository, group your changes into a single commit, and take advantage of Copilot code completion.

You can access Copilot Workspace by choosing to edit an individual file or by clicking Open in Workspace in your pull request's right sidebar. For more information about Copilot Workspace and joining the public preview, see "Using Copilot to help you work on a pull request."

Further reading