Open pedrevans opened 8 years ago
Revisr actually runs git remote update --prune
before running git branch -r
.
According to the docs, git remote update --prune
should be the equivalent of fetching from all remotes, or the same as running git fetch --all --prune
, so it's interesting that this isn't working for you.
It might be worth using fetch instead if that resolves the issue. Can you confirm which version of Git this was happening on?
Sorry about the late answer, I've been away on holiday and just saw this.
I am using git version 1.7.1.
Wow that's pretty old. I'm on an AWS centOS server. In any case I will look into why it's running such an ancient git.
Click on "Remote branches" shows only remote branches that were pushed from one's own working directory, but not remote branches that were created elsewhere and pushed to the remote repository. It's impossible to get Revisr to show the new remote branches and there doesn't seem to be a workaround.
This is
git
behaviour. If you just do agit branch -r
you don't see all the remote branches. You have to do agit fetch
first to get local git to recognise that there are new branches on the remote repository. After thatgit branch -r
works as expected. Revisr needs to dogit fetch
beforegit branch -r
.In the example below you can see that the remote branch
update_plugins_20160620
doesn't show up beforegit fetch
has been done.