There isn't anything to compare. Nothing to compare, branches are entirely different commit histories

that's all there is there isn't anymore madeline
that's all there is there isn't anymore cartoon
there are sentences
there is / there are exercises
that's all there is there ain't no more
there isn't or there aren't
there is or there are a lot
there is and there are worksheets

I have a CMS theme installed on my machine. I'm tracking changes to it via git and decided to back it up on GitHub so I could share those changes.

The theme as provided is also available on GitHub. On my machine I have added this as a remote upstream. Now I can easily see the changes between my master and the remote upstream by using the following command:

git diff --color master upstream/number

If I could add the remote upstream on GitHub I could easily share these changes. Is it possible to set this relationship on GitHub?

I have tried the following:

git push -u origin upstreambranch

which adds an upstreambranch to the master on GitHub. However trying to compare both branches doesn't work, the result I get on GitHub is that: "There isn't anything to compare"

Is there an alternative way to compare these?

The Short Answer

It looks like GitHub won't let you compare the branches because they don't actually share any of the same history at all, even though they may share much of the same files and code.

Here is a screenshot of the temporary fork I made of your repo, where I tried to compare master with the upstreambranch, like you described. Notice the error message:

It says:

There isn't anything to compare.

master and upstreambranch are entirely different commit histories.

The Long Answer

You probably downloaded the original source and added it to a completely new repo instead of cloning the original repo, right? Doing that will make it so that the history of your repo will be completely different from the history of the original repo, since your new repo won't have any of the same commits with the same sha IDs.

You can see that by doing a reverse log of your master branch and the upstreambranch:

# Your first commit, see commit sha
git log --reverse master
commit c548d7b1b16b0350d7fbdb3ff1cfedcb38051397 # <== HERE
Author: Padraic Stack <>
Date:   Wed Apr 2 15:11:28 2014 +0100

    First commit of everything

# First commit sha of the original repo
git log --reverse upstreambranch
commit 105a12817234033c45b4dc7522ff3103f473a862 # <== THERE
Author: Jeremy Boggs <>
Date:   Mon Feb 22 16:00:53 2010 +0000

    Creates repo directories for the Seasons theme.

If you redo your commits on top of the original history, you should then be able to compare the branches. There are several different ways that you can redo your commits, including

git rebase --onto


git cherry-pick

You also can redo each commit manually, if you have to.

There is - there are Interactive worksheet, ID: 601. Language: English School subject: English as a Second Language (ESL​) Level/group: Elementary Age: 9+. Main content: There is - there are “There is” (usually abbreviated to “there’s”) is used for singular or uncountable objects in the affirmative: There is something I have to tell you.

This looks like undesirable behavior on github's part, but it's fairly easy to fix. What you want to do is to rebase your branch on a reasonable (any reasonable) commit in the existing history. What you can do is to fetch the github repo and find which tree in its history is most similar to the one you started with. Start this way:

git remote add github u://r/l
git fetch github

myroot=`git rev-list master --max-parents=0`
root_tree=`git rev-parse $myroot^{tree}`

github_base=`git log --pretty=%H\ %T github/master | sed -n "s/$root_tree//p"`

With any luck, that will find you a commit in the github history that has the exact tree you started with. Assuming it does,

git rebase --onto $github_base $myroot master 

and you're done.

If that doesn't find a matching tree, you get to find a nearest approximation. Here's one way to get a rough estimate of the differences:

git log --pretty='echo %H $(git diff-tree -p -b -U0 '$myroot:' %T|wc -l)' github/master \
| sh

which will count the lines in a minimized diff between the tree of each commit in the github/master history and your root tree. It seems reasonable to hope for a nice small difference, you could eyeball the actual diffs on it before calling that the github_base commit and doing the rebase above.

there isn't much call for something, there isn't much call for something meaning, definition, what is there isn't much call for something: used for saying that not many people wan: Learn more. There’s a new YouTube Music web player for desktop! Rating is available when the video has been rented. This feature is not available right now. Please try again later. Published on Jun 18, 2008

I solve my issue using these commands

git checkout [BRANCH]   
git branch master [BRANCH] -f   
git checkout master   
git push origin master -f

there is, there is. Third-person singular simple present indicative form of there be. Used to indicate the existence of something physical or abstract in a particular place. There isn't any water in the swimming pool. There isn't any sugar in my coffee. Questions. To form a question we place is / are in front of there. Again we use any with plural questions or those which use uncountable nouns. We also use there is / are in short answers. Is there a dog in the supermarket? - No, there isn't. Are there any dogs in

If you know from which commit issue started, you can reset your branch to that commit and then merge them.

There Is There Are - English Grammar Rules, Positive Sentences. We use there is for singular and there are for plural. There is one table in the classroom. There are three chairs in  If I'm not mistaken, both "There isn't a storm." and "There is no storm." have the same meaning. I understand that the first one is the "contraction" of the second one, but what I can't understand is that if it is the contraction of the second, why the is second "There is no storm" and not "There is not storm"?

This happened with me yesterday cause I downloaded the code from original repo and try to pushed it on my forked repo, spend so much time on searching for solving "Unable to push error" and pushed it forcefully.


Simply Refork the repo by deleting previous one and clone the repo from forked repo to the new folder.

Replace the file with old one in new folder and push it to repo and do a new pull request.

There isn't a word for it, There isn't a word for it. Neville Goodman. Additional article information. What was so important about collective nouns? I dug out an old exam paper from around  Hello, I am having a problem with the negative forms of "there isn't a" and "there aren't any". In which situation should we use the singular construction and in which situation should we use the plural construction?

Meaning of "There isn't one", Dima, and welcome to ELU. Your question is an interesting example of presupposition and of a logical conundrum. What you are really  You probably know that the choice between is vs. are depends on a noun. In most sentences, the noun comes before the verb. But in sentences that begin with there is and there are, the noun comes later. There is a cat on the porch. In the sentence above, cat is singular, so it requires there is. There are many opportunities to learn at this company.

“There Isn't Any Such Thing As The Past”, And that there are great lessons in history, and there are. But history is also a source of immense pleasure in the way that music and art and the theater can be​  There is - there are A worksheet to practice "there is", "there are" "there isn't" and "there aren't", and some vocabulary related to the furniture and the food.

There's No Such Thing as Free Will, But there is also agreement in the scientific community that the firing of neurons determines not just some or most but all of our thoughts, hopes, memories, and 

  • It's not clear what you're trying to do. You already pushed your repo up to GitHub? Is it public? If it's public, other people already have access to the code, they can just clone or fork the uploaded repo. "git push -u origin upstreambranch...adds an upstreambranch to the master on GitHub". You don't add branches to "the master on GitHub". Please clarify what you mean.
  • "However trying to compare both branches doesn't work, the result I get on GitHub is that: 'There isn't anything to compare'". Please explain what you're doing to compare branches on GitHub, and include screenshots if possible.
  • I am using a cms called Omeka and a particular theme called Seasons. I have modified this theme and uploaded it here: I would like a visual way (diff) to show people how it is different from the 'original'. I attempted to do so by downloading and then pushing to github this version: In the post above I explained how I did that, but that it didn't work. Does that make more sense?
  • Thanks, that's starting to make a little more sense. Is this the upstream repo that you're referring to? When you say you downloaded the source, did you download it from GitHub or somewhere else, like this site. If you downloaded it from anywhere other than GitHub, then actually doing a fork from GitHub instead would have been better for what you're trying to do, unless this is a customization that you're doing for a specific client that isn't meant to be shared publicly?
  • I figured out what your immediate problem is, but looking at the bigger picture, you might want to reconsider how you're doing everything, as I've already mentioned in my previous comment...but that depends on what you're ultimately trying to do. Writing an answer for your immediate problem...
  • Thanks for your time on this, I appreciate the effort you put in. Your answer lets me know that what I tried to do isn't possible so I am accepting it. Just to be clear though, I did mention the error above when I said However trying to compare both branches doesn't work, the result I get on GitHub is that: "There isn't anything to compare"
  • @Jack your welcome. Yes, you did mention that, but you left out the rest of the error message that says "master and upstream are entirely different histories." That was the key to the issue.
  • @Jack do you know what you need to do to compare branches now? If you redo all of your commits on top of the original history, you can then compare the branches. There are several different ways that you can redo the commits, including git rebase --onto and git cherry-pick.
  • git rebase -i origin/master this worked for me. After doing this I was able to compare both the branches
  • @sujay This is right. After doing that I can compare