Login/Register
How to compare two different commits on the same branch in github?
Asked Answered
Solved gitgithub
I

10

175

Comparing histories on the same branch is very confusing for me on GitHub. I struggle with this regularly:

If I use compare/master in the URL after the GitHub repo name, I can compare against other branches in the repo based on the options in the drop-down menus.

https://help.github.com/en/articles/comparing-commits-across-time

However, I usually want to compare several commits on master.

How is this easily done? Could I get a more clear example?

Immigrate answered 15/4, 2018 at 1:45 Comment(0)
G
312

You can use the following URL structure to compare commits in the same branch:

github.com/<username>/<repo_name>/compare/<commit1>...<commit2>

Replace values for username, repo_name, commit1(old commit) & commit2(new commit) acc. to your project.

The separator between the two commits is ... i.e. 3 dots.

Gujarat answered 15/4, 2018 at 3:0 Comment(10)
3 dots? That's the separator between the two commits? – Vey
Oh, it seems there's a 2-dot notations that shows more info. – Vey
This works fine I wonder why github did not have ui for it and we have to keep modifying urls – Armandoarmature
@lilhamad, There's kind of a UI. Not great, but it's something. #49838269 – Involution
@AlikElzin-kilaka, "3 dots" will compare from the last common commit: git diff $(git merge-base A B) B. "2 dots" directly compares the two commits: git diff A B. Similar to git diff A...B vs git diff A..B – Involution
@AhmedAdewale I find there are lots of very useful features that github can't find space for in the UI! – Karlotta
It seems username is optional, specially if you are already logged into your GitHub account – Handiness
@Karlotta do you have some more examples of such features? – Acceptant
@Ahmed Adewale since there is even an UI, I guess they just ran out of space in the menu and had to prioritize - "should we put a link to the extremely useful compare UI in the menu, or should we put that Insights thing that nobody cares in there?" – Lovelovebird
docs.github.com/en/pull-requests/… – Whelm
I
36

TLDR: Just add /compare at the end of the URL.

You can use the Github Compare UI, which will generate the URL for you. Replace ORG and REPO with your values. The UI only lists branches, but you can also type in any valid Tags (e.g. v1.0.0) or Commit IDs (e.g. 1a2b3c).

https://github.com/ORG/REPO/compare/

GitHub GUI showing compare options

The URLs that get generated are in this format. You can also manually edit the URL with the REFs.

https://github.com/ORG/REPO/compare/REF1...REF2

You can also use "2 dots" (direct diff) instead of "3 dots" (diff from last common commit). Same as git diff A..B vs git diff A...B.

https://github.com/ORG/REPO/compare/REF1..REF2

If you want to compare across forks, then you need to add ORG2:

https://github.com/ORG/REPO/compare/REF1...ORG2:REF2

There is documentation, but I didn't think it was that clear: https://help.github.com/en/github/committing-changes-to-your-project/comparing-commits-across-time

Involution answered 19/11, 2019 at 20:9 Comment(0)
C
5

The article you linked has instructions for comparing commits.

The GitHub comparison tool will accept any revision. Branches, tags, commit IDs, even dates. If you want to compare between two commits, give it the commit IDs. Here's their example.

Cyder answered 15/4, 2018 at 2:52 Comment(6)
How could one compare .27 to .28 for example? github.com/alpacahq/pylivetrader/tree/master/pylivetrader – Flavorous
@Flavorous github.com/alpacahq/pylivetrader/compare/v0.0.27..v0.0.28 – Cyder
Terrific and also all of alpacahq >= May 8 too? – Flavorous
@Flavorous Sorry, I'm not sure what you're asking for. You should ask it as a question. – Cyder
Since, in this example, pylivetrader has dependencies that might have also changed, can all changes throughout github.com/alpacahq be obtained using a date like on and/or after May 8? – Flavorous
@Flavorous They're separate repositories. You could search each of them individually using the Github API. But dependency management is better handled with a package manager like bundler. – Cyder
I
3

Use ~N to compare with N prior commits

Tips like these are often hidden in the docs so I wanted to note it here where people will find it.

compare main 1 commit ago to main now

https://github.com/facebook/react/compare/main~1..main

compare 4 commits prior to this sha 0415b18

https://github.com/facebook/react/compare/0415b18~4...0415b18

Iamb answered 14/7, 2023 at 16:41 Comment(1)
This is the only solution that I've seen that compares changes within the same branch – Titrant
N
2

to see the difference between branches or tags

(branches if no pull request has been made)

Notes:

  • (if a pull request has been made you can see the changes inside the PR, no longer via the compare url)

  • You can use the dropdowns to select different branches or tags: enter image description here

  • take care of the order, eg. https://github.com/PyCQA/mccabe/compare/master...0.6.1 will give no results

  • you can choose between 2-dot (..) or 3-dot (...) notation

to see the difference between commits:

Nutation answered 6/3, 2020 at 21:45 Comment(0)
C
2

Just go to https://github.com/USERNAME/REPOSITORY_NAME/compare to achive the comparing page

enter image description here

Crux answered 16/9, 2020 at 2:42 Comment(0)
P
2

Custom tabs.

Peeps, we can add a compare "custom tab" to the repository, so that we can quickly access this compare tooling.

Here is how.

  • Goto your repo landing page. https://github.com/<YOUR_ORG_NAME/<YOUR_REPO_NAME>
  • Click the "Settings" tab.
  • Click on "Custom tabs".
  • Fill in the "New tab" name.
  • Fill in the URL for compare. https://github.com/<YOUR_ORG_NAME>/<YOUR_REPO_NAME>/compare
  • Click the "Add tab" button

Now go to your repo landing page and you should now see your newly created custom tab along side the other default tabs (Pull requests, Settings and such)

Pang answered 8/2, 2021 at 15:54 Comment(1)
Wow, excellent idea! Deserves far more love and visibility than it's received. – Jewess
K
1

I visit this page often and the top answer is great.

Today I learned you can not only use the commit SHA, but also the release tag!

Here's an example:

https://github.com/rails/rails/compare/v7.0.4...v7.0.5

Karlotta answered 26/5, 2023 at 11:15 Comment(0)
C
0

If you need to compare changes within a branch but on different dates, this is how you can do it:

https://github.com/<ORG_NAME>/<REPO_NAME>/compare/HEAD..HEAD@{4 weeks ago}
https://github.com/<ORG_NAME>/<REPO_NAME>/compare/HEAD@{1 week ago}..HEAD@{2021-06-01}
Curarize answered 16/6, 2021 at 14:2 Comment(0)
F
0

If anyone needs a handy UI, here you go. I made it for my projects, searching and comparing are quite tricky when I troubleshoot for cases. It helps to quickly create comparisons between the branches/tags/commits(hashes) in several clicks.

Chrome extension: GitHub Compare Online

https://chrome.google.com/webstore/detail/github-compare-online/dglncilbcfbjkdpiabohoofgkfabhpab

enter image description here

Filia answered 14/4, 2023 at 21:48 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.