Create pull requests
TFS 2017 | TFS 2015 | TFS 2013
Visual Studio 2019 | Visual Studio 2017 | Visual Studio 2015
Create pull requests (PRs) to change, review, and merge code in a Git repository. You can create PRs from branches in the upstream repository or from branches in your fork of the repository. Your team can review the PRs and give feedback on changes. Reviewers can step through the proposed changes, leave comments, and vote to approve or reject the PRs. Depending on branch policies and other requirements, your PR might need to meet various criteria before you can complete the PR and merge the changes into the target branch.
For PR guidelines and management considerations, see About pull requests.
Prerequisites
- To learn more about permissions and access, see Default Git repository and branch permissions and About access levels.
Create a pull request
You can create a new PR from the Azure DevOps project website, from Visual Studio, or from the Azure DevOps CLI.
From the Azure DevOps project website, you can create a new PR from:
- The Pull requests page.
- A feature branch pushed to your repo.
- An existing PR, by using cherry-pick.
- The Development control in a linked Azure Boards work item.
Create a PR from the Pull requests page
You can create PRs for any branch from your project's Pull requests page on the web.
On the Repos > Pull requests page, select New pull request at upper right.
Select the branch with the changes and the branch you want to merge the changes into, such as the main branch.
Enter your PR details and create the PR.
Create a PR from a pushed branch
Create a PR from a linked work item
You can create a PR directly from an Azure Boards work item linked to the branch.
In Azure Boards, from Backlogs or Queries in the Work view, open a work item that's linked to the branch.
In the Development area of the work item, select Create a pull request.
The link takes you to a page where you can enter your PR details and create the PR.
Add updates with cherry-pick
You can copy commits from one branch to another by using cherry-pick. Unlike a merge or rebase, cherry-pick only brings the changes from the commits you select, instead of all the changes in a branch.
To cherry-pick changes from a completed PR, select Cherry-pick on the PR's Overview page. To copy changes from an active PR, select Cherry-pick from the PR's More options menu. This action creates a new branch with the copied changes. You can then create a new PR from the new branch. For detailed instructions, see Copy changes with cherry-pick.
Switch source and target branches of your pull request
Before the first time you save a PR, you can switch the source and target branches of the PR by selecting the Switch source and target branches icon next to the branch names. Once the PR is active, this icon goes away, but you can still change the target branch of the PR.
Add or edit pull request title and description
On the New pull request page, enter a Title and detailed Description of your changes, so others can see what problems the changes solve. On a new PR as in existing PRs, you can see the Files and Commits in your PR on separate tabs. You can add reviewers, link work items, and add tags to the PR.
When you're ready to have your changes reviewed, select Create to create the PR.
Don't worry if you don't have all of the work items, reviewers, or details ready when you create your PR. You can add or update these items after you create the PR.
Edit PR title and description
Keep the PR title and description up to date so reviewers can understand the changes in the PR.
You can update the title of an existing PR by selecting the current title and updating the text. Select the Save icon to save changes, or select the Undo icon to discard the changes.
Edit the PR description by selecting the Edit icon in the Description section.
