Repos must be enabled on your project. If the Repos hub and associated pages don't display, see Turn an Azure DevOps service on or off to reenable Repos.

To complete your PR, you must be a member of the Contributors security group, or have the corresponding permissions, in the project the PR is in.

To contribute to a PR, you must be a member of the Readers security group or have the corresponding permissions.

To view or review PRs, you must have Basic or higher access to the Azure DevOps project.

If you aren't a member of the project you want to contribute to, get added .

For public projects, users granted Stakeholder access have full access to Azure Repos.

Connect to your project from Visual Studio .

Select View > Team Explorer to open Team Explorer. You can also press Ctrl + \ , Ctrl + M .

From Home , select Pull Requests to view lists of PRs opened by you or assigned to you.

To open a PR in the web portal and view the policies in effect, right-click the PR and select Open in browser .

To see all branch policies that are in effect for a PR, use az repos pr policy list with the required id parameter.

az repos pr policy list --id
                        [--detect {false, true}]
                        [--org]
                        [--query-examples]
                        [--skip]
                        [--subscription]
                        [--top]
Parameters
Parameter
Description
--org
--organization
Azure DevOps organization URL. You can configure the default organization by using az devops configure -d organization=<ORG_URL>. Required if not configured as default or picked up via git config. Example: https://dev.azure.com/MyOrganizationName/.
--query-examples
Recommended JMESPath string. You can copy one of the queries and paste it after the --query parameter in double quotation marks to see the results. You can add one or more positional keywords so suggestions are based on these keywords.
--skip
Number of policies to skip.
--subscription
Name or ID of subscription. You can configure the default subscription by using az account set -s <NAME_OR_ID>.
--top
Maximum number of policies to list.
Example
For example, to see the policies in effect on PR #28, run the following command:
az repos pr policy list --id 28 --output table
Evaluation ID                         Policy                                         Blocking    Status    Expired    Build ID
------------------------------------  ---------------------------------------------  ----------  --------  ---------  ----------
84e7ca6d-0b42-4819-9f62-f41df5e319f3  Minimum number of reviewers (1)                True        Approved
1ba061d8-9e9f-401b-ab61-e2ed1c200aba  Required reviewers (1)                         True
37620a4b-adc4-483d-9ca2-3f4e6ffe2990  Comment requirements                           False       Approved
34b7cae8-812a-4c14-9229-f71a0e662e8b  Required reviewers (1) ([Fabrikam Fiber]\Web)  False
a6e4380e-9f38-4aa5-863c-0fc496027362  Work item linking                              False       Rejected
Select Complete at upper right to complete the PR. Or select the dropdown arrow next to the Complete button, and select one of the options.
Complete: Complete the PR now, and merge the changes to the target branch.
Set auto-complete: Configure the PR to complete and merge once it meets all required branch policies.
Mark as draft: Return the PR to draft status and remove all votes.
Abandon: Close the PR without merging the changes.
In the Complete pull request pane, under Merge type, select one of the merge options.
Merge (no fast forward): Merge with a non-linear history that preserves all commits.
Squash commit: Merge with a linear history that combines all source commits into a single commit on the target, or squash merges the PR. Be aware that a new commit will be created for the target branch without keeping the commit history from the source branch.
Rebase and fast-forward: Rebase the source commits onto the target and fast-forward.
Semi-linear merge: Rebase source commits onto the target and create a two-parent merge.
Existing policies are enforced. For example, if your branch currently has a "squash merge only" policy, you have to change that policy if you want to use another merge type.
Select any of the following post-completion options. Some options aren't available for some merge types.
Complete associated work items after merging: Complete any linked work items.
Delete <branch name> after merging: Delete the PR's source branch after merging.
Customize merge commit message: Add a custom merge commit message. If you select this option, update the merge commit message.
Override branch policies and enable merge. Force the merge even if the PR doesn't satisfy all branch policies. This option is only available if you have Exempt from policy enforcement permission.
Select Complete merge.
Select Complete at upper right to complete the PR. Or, select the dropdown arrow next to the Complete button, and select one of the following options:
Complete: Complete the PR now, and merge the changes to the target branch.
Set auto-complete: If you have branch policies, configure the PR to complete and merge once it meets all required branch policies.
Abandon: Close the PR without merging the changes.
On the Complete pull request screen, enter the message for the merge commit and update the PR description.
Select any of the following options:
Complete linked work items after merging to complete any linked work items.
Delete <branch name> after merging to delete the source branch from the PR.
Squash changes when merging to squash merge your PR. Be aware that a new commit will be created for the target branch without keeping the commit history from the source branch.
Override branch policies and enable merge to force a branch to merge even if it doesn't satisfy all branch policies. This option is only available if you have Exempt from policy enforcement permissions.
Existing policies are still enforced. For example, if your branch currently has a "squash merge only" policy in place, you have to edit that policy in order to use the other merge types.
Select Complete in the upper right of the PR view to complete your PR after the reviewers approve of the changes.
Complete: Complete the PR now and merge the changes to the target branch.
Set auto-complete: If you have branch policies, you can choose Set auto-complete to configure the PR to close once it meets all branch policies.
Abandon: Close the PR without merging the changes.
In Complete pull request, enter the message for the merge commit and update the PR description.
Select any of the following post-completion options:
Complete linked work items after merging to complete any linked work items.
Delete <branch name> after merging to delete the source branch from the PR.
Squash changes when merging to squash merge your PR. Be aware that a new commit will be created for the target branch without keeping the commit history from the source branch.
Override branch policies and enable merge to force a branch to merge even if it doesn't satisfy all branch policies. This option is only available if you have Exempt from policy enforcement permissions.
Select Complete merge.
Linked work items are also updated showing the PR completion.
To complete a PR, open the PR in the browser, and on the Overview page, select Complete or set other options.
To open a PR from Visual Studio, in the Git menu, select <your Git service> > View Pull Requests, and select a pull request to open it.
To access PRs from Visual Studio 2019 Team Explorer:
Connect to your project from Visual Studio.
Select View > Team Explorer to open Team Explorer. You can also press Ctrl+\, Ctrl+M.
From Home, select Pull Requests to view lists of PRs opened by you or assigned to you.
To open a PR in the web portal, right-click the PR and select Open in browser.
To complete a PR and merge the changes, use az repos pr update to update the PR --status to completed.
For example, to complete PR #21, use:
az repos pr update --id 21 --status completed
Set completion options
You can set PR completion options when you create a PR with az repos pr create, or update creation options in existing PRs with az repos pr update.
PR completion options include:
bypass-policy {false, true}: Whether to bypass any required policies and complete the pull request once it can be merged.
bypass-policy-reason: Reason for bypassing required policies.
delete-source-branch {false, true}: Whether to delete the source branch after the pull request has been completed and merged.
merge-commit-message: Customize the merge commit message.
squash {false, true}: Whether to squash the source commits into a single target commit for merge.
transition-work-items {false, true}: Whether to resolve linked work items when the PR merges.
To set completion options and complete an existing PR, use az repos pr update with the required id parameter.
az repos pr update --id
                   [--auto-complete {false, true}]
                   [--bypass-policy {false, true}]
                   [--bypass-policy-reason]
                   [--delete-source-branch {false, true}]
                   [--description]
                   [--detect {false, true}]
                   [--draft {false, true}]
                   [--merge-commit-message]
                   [--org]
                   [--squash {false, true}]
                   [--status {abandoned, active, completed}]
                   [--subscription]
                   [--title]
                   [--transition-work-items {false, true}]
Parameters
Parameter
Description
--auto-complete
Set the pull request to complete automatically when all policies have passed and the source branch can be merged into the target branch. Accepted values: false, true.
--bypass-policy
Bypass any required policies and complete the pull request once it can be merged. Accepted values: false, true.
--bypass-policy-reason
Reason for bypassing required policies.
--delete-source-branch
Delete the source branch after the pull request is completed and merged into the target branch. Accepted values: false, true.
--description -d
New description for the pull request. Can include Markdown. Each value is new line. For example: --description "First Line" "Second Line".
--detect
Automatically detect organization. Accepted values: false, true.
--draft
Convert the PR to draft mode or publish it. Accepted values: false, true.
--merge-commit-message
Message to display when commits are merged.
--org
--organization
Azure DevOps organization URL. You can configure the default organization by using az devops configure -d organization=<ORG_URL>. Required if not configured as default or picked up via git config. Example: https://dev.azure.com/MyOrganizationName/.
--squash
Squash the commits in the source branch when merging into the target branch. Accepted values: false, true.
--status
Set the new state of pull request. Accepted values: abandoned, active, completed.
--subscription
Name or ID of subscription. You can configure the default subscription by using az account set -s <NAME_OR_ID>.
--title
New title for the pull request.
--transition-work-items
Transition any work items linked to the pull request into the next logical state, for example Resolved. Accepted values: false, true.
Example
The following example completes PR #21, deletes its source branch, resolves its linked work items, and adds a merge commit message:
az repos pr update --id 21 --status completed --delete-source-branch true --transition-work-items true --merge-commit-message "This update is complete."
Azure DevOps CLI commands aren't supported for Azure DevOps Server on-premises.
Rebase during PR completion
There are a few situations when rebasing during PR completion isn't possible:
If a policy on the target branch prohibits using rebase strategies, you need Override branch policies permission to rebase.
If the PR source branch has policies, you can't rebase it. Rebasing would modify the source branch without going through the policy approval process.
If you used the Merge Conflict Extension to resolve merge conflicts, you can't rebase. Conflict resolutions applied to a three-way merge are seldom successful or valid when rebasing all the PR commits individually.
In all these cases, you can still rebase your branch locally and then push upstream, or squash-merge your changes when you complete the PR.
Multiple merge base issue
In some cases, a PR has more than one true merge base, and this situation can cause security issues. If the files in the PR have different versions between the merge bases, a multiple merge base warning happens. For more information and remediation, see Multiple merge bases.
Resolve merge conflicts
File changes in your branch can conflict with changes in another branch. When it isn't clear how to merge changes, Git shows the files that conflict on the PR's Overview page. You must resolve any merge conflicts between the PR branch and the target branch before you can merge a PR or set the PR to autocomplete. For instructions on resolving merge conflicts, see Resolve merge conflicts.
Set a pull request to autocomplete
Browser
Visual Studio
Azure DevOps CLI
Select Set auto-complete from the Complete dropdown list to complete and merge the PR changes as soon as conditions satisfy all branch policies. When the PR is completed, you receive an email notification. If a conflict or error prevents PR completion, email notifies you of the issue.
The Set auto-complete option is available in Azure Repos and TFS 2017 and higher when you have branch policies. If you don't see Set auto-complete, you don't have any branch policies. For more information, see Branch policies.
By default, a PR that's set to autocomplete waits only on required policies. In the Enable automatic completion panel, you can choose to wait on optional policies as well.
Starting with TFS 2018 Update 2, the PR Overview page displays the list of outstanding policy criteria the PR is waiting for. If you set a policy to be required in the Enable automatic completion panel, you can set it back to optional on the Overview page.
Select Cancel auto-complete to turn off autocomplete.
Open a pull request in the web portal. On the Overview page, select Set auto-complete.
To open a PR from Visual Studio, in the Git menu, select <your Git service> > View Pull Requests, and select a pull request to open it.
To access PRs from Visual Studio 2019 Team Explorer:
Connect to your project from Visual Studio.
Select View > Team Explorer to open Team Explorer. You can also press Ctrl+\, Ctrl+M.
From Home, select Pull Requests to view lists of PRs opened by you or assigned to you.
To open a PR in the web portal and view the policies in effect, right-click the PR and select Open in browser.
Set autocomplete to complete a PR automatically when it passes all required approvals and branch policies. You can set autocomplete at PR creation, or update an existing PR.
To set autocomplete at PR creation, use az repos pr create --auto-complete true.
To update an existing PR to autocomplete, use az repos pr update --id <PR Id> --auto-complete true.
Azure DevOps CLI commands aren't supported for Azure DevOps Server on-premises.
To abandon your changes and your PR without merging, select Abandon from the dropdown list on the Complete button. You can still view the abandoned PR, and it stays linked to work items.
To reactivate an abandoned PR at any time, open the PR from the Abandoned tab in the Pull Request view, and select Reactivate at upper right.
To abandon a PR without merging the changes, use az repos pr update --id <PR Id> –-status abandoned. You can reactivate the PR by setting the status to active.
Azure DevOps CLI commands aren't supported for Azure DevOps Server on-premises.
Revert a completed pull request
To undo the changes from a PR, follow these steps. For more information, see Undo changes.
Open the completed PR and select Revert. This action creates a new branch with changes that undo the PR in an existing target branch in your repo.
In the Revert pull request pane:
Under Target branch, select the branch where you want to undo the PR changes.
Under Topic branch name required, change the revert PR branch name if you want.
Select Revert.
On the New pull request screen, select Create.
Merge the new PR to complete the revert.
The branch created during this revert has a single commit that reverts all the file changes from the original PR. The branch doesn't contain a reverted commit for each of the commits in the original PR.
Next steps
Copy changes with cherry-pick
Related articles
Pull request update notifications
About pull requests and permissions