Creating a pull request – GitHub Docs

If you want to create a newfangled arm 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 pitchfork “ and “ About forks. ”
You can specify which branch you ‘d like to merge your changes into when you create your rend request. Pull requests can lone be opened between two branches that are different .
Note : To open a pull request in a populace depository, you must have write access to the head or the informant 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 draw request to an write out to show that a localization is in build up and to mechanically close the return when person 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 depository ‘s default outgrowth. For more information, see “ About branches. ”
If the default option parent depository is n’t chastise, you can change both the parent repository and the branch with the drop-down lists. You can besides 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 depository .
Pull Request editing branches
When thinking about branches, remember that the nucleotide outgrowth is where changes should be applied, the point arm contains what you would like to be applied .
When you change the floor depository, you besides change notifications for the pull request. Everyone that can push to the base depository will receive an e-mail notification and see the new pull request in their dashboard the following time they sign in .
When you change any of the information in the ramify rate, 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.com, navigate to the main page of the repository.
  2. In the “Branch” menu, choose the branch that contains your commits.
    Branch dropdown menu
  3. Above the list of files, click Pull request.
    "Pull request" link above 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.
    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. 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. For more information about draft pull requests, see “About pull requests.”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 depository.

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 extract 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 extract 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 blueprint, use the --draft flag .

gh pr create --draft

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

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

To add the newly 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 nonpayment web browser, use the --web flag .

gh pr create --web
  1. Switch to the branch that you want to create a pull request for. For more information, see “Switching between branches.”
  2. Click Create Pull Request. GitHub Desktop will open your default browser to take you to GitHub.
    The Create Pull Request button
  3. On GitHub, confirm that the branch in the base: drop-down menu is the branch where you want to merge your changes. Confirm that the branch in the compare: drop-down menu is the topic branch where you made your changes.
    Drop-down menus for choosing the base and compare branches
  4. Type a title and description for your pull request.
    Pull request title and description fields
  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. For more information about draft pull requests, see “About pull requests.”Create pull request button
  1. Switch to the branch that you want to create a pull request for. For more information, see “Switching between branches.”
  2. Click Create Pull Request. GitHub Desktop will open your default browser to take you to GitHub.
    The Create Pull Request button
  3. On GitHub, confirm that the branch in the base: drop-down menu is the branch where you want to merge your changes. Confirm that the branch in the compare: drop-down menu is the topic branch where you made your changes.
    Drop-down menus for choosing the base and compare branches
  4. Type a title and description for your pull request.
    Pull request title and description fields
  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. For more information about draft pull requests, see “About pull requests.”Create pull request button
  1. Once you’ve committed changes to your local copy of the repository, click the Create Pull Request icon.
    Source control side bar with staging button highlighted
  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.
    GitHub pull request side bar
  3. Click Create.

For more information on creating pull requests in Codespaces, see “ Using Codespaces for pull requests. ”

Further reading

Related Posts

Leave a Reply

Your email address will not be published.