Web Applications Stack Exchange is a question and answer site for power users of web applications. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On github, how can I find the repositories I have forked but are still identical to the parent repository (i.e. no changes were made in the fork)?

share|improve this question

migrated from superuser.com Apr 27 '12 at 5:51

This question came from our site for computer enthusiasts and power users.

Maybe you can use the Updated before the date Repositories Option in advanced search. – N.N. Mar 6 '13 at 6:37
up vote 2 down vote accepted

Painstakingly and one by one.

There isn't anything to show you at a glance all your project forks which share the same commit revision history or are different in some way to the original repo.

For each of the original repos you want to compare against, click on their respective Network Graphs at the following URL type:


The original repo will be at the top (base reference point) and list a few other repos in timelines below it. All branches and commits are marked out in the first line. Any commits or branches that forked versions contain, but are not in the original, will show up as competing racing lines in the graph.

Example network graph

original-repo     |---*----*----*----*------------*--*-*----------***----*-
                                     |               |
toothygrinmeister |                  |--------*      |
cuddlebucketeer   |                                  |------*--*-*

In this example, both toothygrinmeister and cuddlebucketeer have commits that original-repo does not. Should either one of these users issue a pull request and their code is rolled back into original-repo, then the respective dots on the graph would disappear.

Similarly, if your fork does not appear on the network graph when viewing against the master as the zero point, then you can assume your fork is up to date and matches that repository's commit history.

share|improve this answer
Using the network graph is a good idea indeed. Thank you. – ℝaphink Sep 17 '12 at 8:25

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.