1163

How can I see the diff between a local branch and a remote branch?

c69
  • 16,477
  • 6
  • 47
  • 78
mrblah
  • 88,033
  • 134
  • 292
  • 404
  • 8
    This questions was asked again later. It has a nice answer: http://stackoverflow.com/questions/11935633/git-diff-between-remote-and-local-repo – rustybeanstalk Oct 17 '13 at 05:27
  • 5
    example: git diff master origin/master (where master is local master branch and origin/master is remote master branch). – Dung May 01 '17 at 17:56
  • @klyngbaek, this [answer](https://stackoverflow.com/a/33289679/8554766) in particular ;-) –  Sep 11 '18 at 08:52
  • I was originally trying `git diff HEAD origin/HEAD` which seems to point to a different remote branch than the one I intended. Using the full branch name works as expected. – Deanna Dec 03 '18 at 15:44

23 Answers23

1337
git diff <local branch> <remote>/<remote branch>

For example git diff main origin/main, or git diff featureA origin/next

Of course to have said remote-tracking branch you need to git fetch first; and you need it to have up to date information about branches in remote repository.

Janusz
  • 176,216
  • 111
  • 293
  • 365
Jakub Narębski
  • 268,805
  • 58
  • 209
  • 228
  • 100
    to be more exact: git diff / – nalply Jul 27 '11 at 10:02
  • 42
    I usually do `git diff / ` to see what my push will do to remote repo. – Michał Tatarynowicz Aug 12 '13 at 12:51
  • 87
    The even shorter `git diff origin` is sufficient if you just compare with your upstream branch. – Ludder Apr 10 '14 at 12:40
  • 16
    please add `git fetch` at the beginning,it cause trouble to newbie like me – Saif Mar 25 '15 at 15:59
  • The `git branch -a` below really completes the picture. It shows you all of your remote branches, for easy diff'ing. – Mike S Sep 03 '15 at 21:04
  • 3
    Hey, shouldn't it be `git diff / `? Otherwise, I get the adds and deletes switched on my computer (git version 2.7.0.windows.2) – Martín Coll Feb 06 '16 at 00:48
  • 1
    @Ludder, I think you meant `git diff @{upstream}` instead? `git diff origin` always shows me `origin/master` no matter what branch I have checked out. – carej Mar 15 '16 at 23:00
  • `origin` expands to the default branch, not the tracked branch. – Niels Keurentjes May 18 '16 at 18:58
  • @carej and @NielsKeurentjes: `origin` expands to what `origin/HEAD` points to, i.e. default branch; you can change where `origin` as a branch shortcut points to with the `git remote` command (in modern Git). – Jakub Narębski May 19 '16 at 10:22
  • 1
    `git diff master origin/master` will only show differences if they have been committed, `git diff origin` or `git diff @{upstream}` will show differences even if they have not been committed. – Akavall Feb 12 '17 at 03:49
  • 1
    Order matters. For ex., `git diff master origin/master` will show, what difference is present in remote file (compared to local _commited_ file), while `git diff origin/master master` will show, what difference is present in file from local repository (ie, commited) compared to remote file. And `git diff origin` is the same as `git diff origin/master master` **+** uncommited changes. – Boolean_Type Apr 23 '17 at 16:57
709

To update remote-tracking branches, you need to type git fetch first and then :

git diff <mainbranch_path> <remotebranch_path>

You can git branch -a to list all branches (local and remote) then choose branch name from list (just remove remotes/ from remote branch name.

Example: git diff main origin/main (where "main" is local main branch and "origin/main" is a remote namely origin and main branch.)

Janusz
  • 176,216
  • 111
  • 293
  • 365
meder omuraliev
  • 171,706
  • 64
  • 370
  • 423
  • 36
    He may need a fetch before (`git fetch`) – Houssem Badri Sep 10 '18 at 12:03
  • 2
    That just shows a sneak into the changes in bash, is there any way to open all changes in an IDE like VS code? – Harsh Phoujdar May 05 '20 at 08:37
  • @Harsh Phoujdar Add the below code in your .git/.gitconfig file `[diff] tool = vscode [difftool] prompt = false [difftool "vscode"] cmd = \"C:\\Program Files (x86)\\Microsoft VS Code\\Code.exe\" \"$LOCAL\" \"$REMOTE\" --diff --wait trustExitCode = false` Make sure your path to code.exe file is correct. – Aman May 05 '20 at 19:59
  • On VS Code there is the [Git Lens](https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens) extension that is very helpfull on this and many other ways. On new GitLens tab > Repositories: There is a list of all files changed by commits ahead with a side-by-side preview on click. – Traxidus Wolf Jun 28 '20 at 09:59
190

First type

git branch -a

to get the list of available branches. On the output you may see something like

* master
  remotes/main/master
  remotes/origin/HEAD -> origin/master
  remotes/origin/master
  remotes/origin/mt
  remotes/upstream/master
  remotes/upstream/mt

Then show the diff

git diff --stat --color remotes/main/master..origin/master
git diff remotes/main/master..origin/master
YSN
  • 2,282
  • 1
  • 12
  • 12
  • 1
    shouldn't it be `...` rather than `..`? – Eliran Malka Apr 09 '13 at 09:27
  • 9
    I would definitely have chosen this as the answer. Following your directions, I was able to view the differences between a local branch and a remote branch. Thanks! – Tass May 28 '13 at 17:10
  • 1
    I usually do `git log origin/my_branch..` which will take `HEAD` as local ref, which is mostly what you mean. – Rudie Oct 22 '13 at 21:15
  • 4
    +1 for best answer in my humble opinion. Would be worthy of +2 if you mentioned "fetch" to synchronize the "remote" image of the cloned source. The stat/color overview step is particularly helpful. – bvj Sep 04 '14 at 05:39
  • As diff is about two endpoints, and not about revision range like log, therefore `git diff A..B` is `git diff A B`, and `git diff A...B` is `git diff $(git merge-base A B) B` - the syntax is to make it possible to copy'n'paste `git fetch` output both to `git log` and `git diff`. – Jakub Narębski Sep 04 '15 at 15:14
  • Why dots at all between the branches being diff'd? Is that any different than just using a space? Edit: documentation is at https://git-scm.com/docs/git-diff – J Woodchuck Nov 08 '17 at 16:42
  • 3
    Thanks for the one answer that finally worked out of the seven or eight "answers" that resulted in little more than `fatal: bad revision` or `fatal: ambiguous argument`. All I wanted was to see the diff on the same file from another branch, was that too much to ask? Yes, yes it was. :-) `git diff remotes/origin/ -- ` works great on git 1.8.3.1 – Steve Bonds Apr 25 '18 at 21:22
181

If you're on a given branch, and you want to compare your working copy with the upstream branch you're tracking, use:

git diff @{upstream}

If you want to compare your current HEAD with the upstream branch (thanks @Arijoon):

git diff @ @{upstream}

If your upstream isn't set, you can use @{push} to get a diff against the branch you are set to push to (also from @Arijoon's comment):

git diff @{push}

Courtesy of this answer, the git documentation for specifying revisions has:

<branchname>@{upstream}, e.g. master@{upstream}, @{u}
The suffix @{upstream} to a branchname (short form <branchname>@{u}) refers to the branch that the branch specified by branchname is set to build on top of (configured with branch.<name>.remote and branch.<name>.merge). A missing branchname defaults to the current one.

rob74
  • 3,867
  • 22
  • 29
Andrew Grimm
  • 70,470
  • 47
  • 186
  • 310
  • 16
    Very good answer just missing a little part. Change the line to `git diff @ @{upstream}`. The extra `@` is `HEAD`, which is where you are now, so you are comparing `HEAD` with the upstream your branch is tracking. You can use `@{push}` instead of upstream to get diff between the branch you are set to push to – Arijoon Apr 01 '17 at 14:21
  • 6
    best answer, doesn't require fetching the remote. needs more upvotes! – jcomeau_ictx Jun 16 '17 at 17:24
  • 3
    In fish shell I got result: `fatal: ambiguous argument '@upstream': unknown revision or path not in the working tree`. Had to use `git diff @\{upstream\}` instead. – Landon Kuhn Sep 20 '17 at 17:13
  • You need to `git fetch` first, else this does nothing, shows no output; tested by deleting a file in the repo origin and ran this command locally. ..works only after fetch. –  Nov 21 '18 at 21:44
  • Also, as the answer as given includes any local changes. sometimes this is desired, other times, not. – Deanna Dec 03 '18 at 15:46
  • `fatal: ambiguous argument '@{origin}': unknown revision or path not in the working tree.`. Based on comment above about problem with fish *(I'm on zsh though)*, I made it to somewhat work as `git diff @\\{origin\\}`. However the diff was empty, even though I changed one commit and I know it shouldn't be. So no, this answer doesn't work at all. – Hi-Angel Aug 12 '19 at 07:28
  • `fish`/`zsh`, comment the argument with single quotes so that no shell replacement happens. i.e. `git diff @ '@{u}'`. Read the shell manual to understand the replacment rules for your shell. Quoting with single quotes will work in _all_ shells though. – Matt Clarkson Jan 22 '20 at 09:35
45

I understand much better the output of:

git diff <remote-tracking branch> <local branch>

that shows me what is going to be dropped and what is going to be added if I push the local branch. Of course it is the same, just the inverse, but for me is more readable and I'm more confortable looking at what is going to happen.

manfer
  • 467
  • 4
  • 2
32

The easy way:

git fetch
git log -p HEAD..FETCH_HEAD

This will first fetch the changes from your default remote (origin). This will be created automatically when you clone a repo. You can also be explicit: git fetch origin master.

Then git log is used to compare your current branch with the one just fetched. (The -p (generate patch) option is what shows the differences.)

gipinani
  • 12,376
  • 10
  • 50
  • 80
Brent Faust
  • 8,214
  • 4
  • 47
  • 52
16

This is how I do it.

#To update your local.
git fetch --all

this will fetch everything from the remote, so when you check difference, it will compare the difference with the remote branch.

#to list all branches
git branch -a

the above command will display all the branches.

#to go to the branch you want to check difference
git checkout <branch_name>
#to check on which branch you are in, use
git branch
    (or)
git status

Now, you can check difference as follows.

git diff origin/<branch_name>

this will compare your local branch with the remote branch

Sahith Vibudhi
  • 3,207
  • 1
  • 20
  • 25
  • 2
    git fetch --all will fetch everything from ALL remotes. git fetch should be sufficient if you use the default origin remote. – Christophe Keller Jun 19 '17 at 06:58
  • Amazing that after 8 years, we get a complete answer that properly explains the steps. We can do a --help to get the commands. SO is about understanding them. – gdbj Aug 02 '17 at 14:27
12

tl;dr: git diff <local branch> <remote branch>

When using git on the shell, I like to first orient myself by looking around. Here's a command to show all branches

$ git branch -a  # (or git branch --all) 
* my-branch
  master
  remotes/origin/some-branch
  remotes/origin/HEAD -> origin/master
  remotes/origin/my-branch
  remotes/origin/some-other-branch
  remotes/origin/master

Here I have two local branches (my-branch and master) and 4 remote (some-branch, some-other-branch, master, and my-branch).

Also, the asterisk next to my-branch signals the fact that I'm currently in that branch (you would also know that by using the command git status that would output: On branch my-branch.).

Note: the remote branches in the git bash shell are shown in red while the local ones are shown in green.

If you just want to show remote branches:

$ git branch -r # (or git branch --remotes)
  origin/some-branch
  origin/HEAD -> origin/master
  origin/my-branch
  origin/some-other-branch
  origin/master

To show just local branches you might be tempted to use git branch -l but that's a completely different command. To show local branches use git branch with no options

$ git branch
* my-branch 
  master

To complete a review of the basic branch options there's the --list that contrary to what you might expect is there to allow filtering. Use it with a pattern like this:

$ git branch --list 'my*'
* my-branch

You can also combine --list with the options -a and -r but make sure to adapt your pattern accordingly (remember: remote branches start with "remotes"). Example:

# this will show all branches (local & remote) that start with my
$ git branch --list 'my*' -a
* my-branch

# better: the pattern includes the remote
$ git branch --list '*my*' -a
* my-branch
  remotes/origin/my-branch

Docs: https://git-scm.com/docs/git-branch

Now you can compare any two branches from all the available ones (you can also compare two locals or two remotes).

Here I'm comparing the local with the remote my-branch, they're synchronized so I don't get any output:

$ git diff my-branch remotes/origin/my-branch

Note: you have to give the full names of the branches with no quotation marks.

I can also compare the local my-branch to the remote master. Here I get some output because the remote my-branch hasn't been merged into the master branch.

$ git diff my-branch remotes/origin/master
diff --git a/src/controllers/call.controller.js b/src/controllers/call.controller.js
index fd79b98..df3d798 100644
--- a/src/controllers/call.controller.js
+++ b/src/controllers/call.controller.js
@@ -261,7 +261,7 @@ function callController() {
   /*
    *  Function: doCall
[ . . . ]
user2314737
  • 21,279
  • 16
  • 81
  • 95
11

Let your working branch is development and want to differentiate between local development branch and remote development branch, that case, syntax should be like git diff remotes/origin/development..development
or

git fetch origin git diff origin/development

Ratna Halder
  • 1,744
  • 15
  • 15
11

If you want to see the difference as just the names of the files changed then use:

git diff --name-status <remote-branch> <local-branch>,

else this would show all differences between the two branches:

git diff <remote-branch> <local-branch>

9

Here is a shorthand answer if you are comparing your current branch and to something you want to git pull.

git fetch
git diff FETCH_HEAD

The first command will figure out which remote branch corresponds to your current branch. An artifact of that calculation in the FETCH_HEAD reference. Then the second command uses that reference compare versus what your current branch has.

William Entriken
  • 30,701
  • 17
  • 128
  • 168
6

I know there are several answers to this question already but I was getting an odd error when trying most of them.

In my case I have a second remote called heroku that is not the origin and because it wasn't in sync I got this error when trying to run the git diff master heroku/master:

fatal: ambiguous argument 'heroku/master': unknown revision or path not in the working tree.

or this when trying the other approach git diff master..heroku/master:

fatal: bad revision 'master..heroku/master'

The solution was explicitly mentioning the remote name on git fetch before running git diff, in my case:

$ git fetch heroku
$ git diff master heroku/master

Hope that helps others with this same issue.

fagiani
  • 1,961
  • 2
  • 22
  • 26
5
git difftool <commit> .

This will compare the commit you want with your local files. Don't forget the dot in the end (for local).

For example, to compare your local files with some commit:

git difftool 1db1ef2490733c1877ad0fb5e8536d2935566341 .

(and you don't need git fetch, unless comparing to new commits is needed)

Izik
  • 422
  • 3
  • 14
  • I think tis is interesting because is a comparison I can make before commit and push. Unfortunately in windows vimdiff for showing is ugly; is there any way to use anything better, like notepad++? – Stefano Scarpanti Aug 01 '17 at 10:22
2

Example

git diff 'master' 'testlocalBranch'

If you are using editor like webstorm, you can right click on file select compare with branch and type/select your branch.

enter image description here

enter image description here

Kurkula
  • 6,673
  • 23
  • 99
  • 170
  • 2
    What does this add over the 7.5 year old accepted answer with 170+ upvotes? – Mark Rotteveel Apr 15 '17 at 08:42
  • This is For mrblah the user or for similar users who added comment for the accepted answer. Syntax is different from an example and example helps more from beginner's point of view. – Kurkula Apr 15 '17 at 14:55
  • 2
    In that case, it should be in comment of that answer. – rachit Sep 20 '17 at 13:39
2

try:

git diff origin HEAD

Assuming you want to diff you current Local branch's HEAD against the origin. And assuming you are on the local branch. :)

N. berouain
  • 973
  • 12
  • 16
1

In VS 2019, just do FETCH Do not pull code.

This is what I did. Added below in .gitconfig file so that I can use Beyond Compare

File location: C:\Users\[username]\.gitconfig

Added below

[diff]
    tool = bc
[difftool "bc"]
    path = c:/Program Files/Beyond Compare 4/bcomp.exe

Open command prompt and go to working directory. I gave below to compare local DEV branch to remote DEV branch

git difftool dev origin/dev --dir-diff

This will open Beyond Compare and open directories which have files that differ. If no changes Beyond Compare will not launch.

Ziggler
  • 2,634
  • 3
  • 31
  • 50
0

I wonder about is there any change in my master branch...

  1. Firstly, you need to change your branch (If you are already under this branch, you do not need to do this!)

git checkout master

  1. You can see which file has been modified under your master branch by this command

git status

  1. List the branches

git branch -a

  • master
    remotes/origin/master
  1. Find the differences

git diff origin/master

Community
  • 1
  • 1
Ali Atakan
  • 349
  • 3
  • 5
0

This is quite simple. You can use: git diff remote/my_topic_branch my_topic_branch

Where my_topic_branch is your topic branch.

Elisha Senoo
  • 3,019
  • 2
  • 20
  • 28
0

Let's say you have already set up your origin as the remote repository. Then,

git diff <local branch> <origin>/<remote branch name>

Tirtha
  • 317
  • 2
  • 6
0

In android studio, it is possible to see the difference between branches using graphical interface. Select your remote branch and and "Compare with current" from the list. From then you can select the files tab to see if there are any files that have content difference between both branches. If no file is seen, then both branches are up-to-date with each other.

The_Martian
  • 3,083
  • 2
  • 26
  • 50
0

For count of different commits from HEAD to origin/master:

git remote update
git rev-list HEAD..origin/master --count

To get current HEAD commit hash id:

git rev-parse HEAD

To get remote origin/master commit hash id:

git rev-parse origin/master
Shahbaz
  • 306
  • 5
  • 15
-1

Setup

git config alias.udiff 'diff @{u}'

Diffing HEAD with HEAD@{upstream}

git fetch  # Do this if you want to compare with the network state of upstream; if the current local state is enough, you can skip this
git udiff

Diffing with an Arbitrary Remote Branch

This answers the question in your heading ("its remote"); if you want to diff against "a remote" (that isn't configured as the upstream for the branch), you need to target it directly. You can see all remote branches with the following:

git branch -r

You can see all configured remotes with the following:

git remote show

You can see the branch/tracking configuration for a single remote (e.g. origin) as follows:

git remote show origin

Once you determine the appropriate origin branch, just do a normal diff :)

git diff [MY_LOCAL] MY_REMOTE_BRANCH

DylanYoung
  • 1,835
  • 22
  • 27
-3

If you use TortoiseGit (it provides GUI for Git), you can right click your Git repo folder then click Git Sync.

You can select your branches to compare if not selected. Than you can view differences commit. You can also right click any commit then Compare with previous revision to view differences side by side.tortoise git sync to compare remote and local branch