Skip to content

Commit 52becea

Browse files
authored
Merge pull request #5178 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-devops-docs (branch main)
2 parents 4692efa + 45eb099 commit 52becea

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

docs/repos/git/review-pull-requests.md

+16
Original file line numberDiff line numberDiff line change
@@ -148,6 +148,22 @@ On the PR **Overview** tab, you can review the PR description and comments to un
148148

149149
Select the PR **Files** tab to view the actual changes made to the source branch next to the target branch of the pull request.
150150

151+
> [!NOTE]
152+
> The different changes between Azure DevOps Pull request and Azure DevOps Branch compare is caused by the different comparison methods.
153+
154+
There are two comparison methods for the git diff command. Two-dot (```git diff A..B```) and three-dot (```git diff A...B```). By default, pull requests show a three-dot diff while the Branch Comparison instead shows a two-dot diff.
155+
156+
For example:
157+
```
158+
C---D---E branch
159+
/
160+
A---B---F---G master
161+
```
162+
163+
```git diff branch..master``` will retrieve C, D, E, F, G commits. While ```git diff branch...master``` will produce only F, G.
164+
165+
Here are the relevant documentations about the git diff commands: [three-dot-and-two-dot-git-diff-comparisons](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests#three-dot-and-two-dot-git-diff-comparisons) & [git diff](https://git-scm.com/docs/git-diff)
166+
151167
:::image type="content" source="media/review-pull-requests/2020/pull-request-files.png" alt-text="Screenshot of a file diff view in the Files tab of an Azure Repos PR.":::
152168

153169
> [!NOTE]

0 commit comments

Comments
 (0)