You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 a git branch -r you don't see all the remote branches. You have to do a git fetch first to get local git to recognise that there are new branches on the remote repository. After that git branch -r works as expected. Revisr needs to do git fetch before git branch -r.
In the example below you can see that the remote branch update_plugins_20160620 doesn't show up before git fetch has been done.
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?
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.The text was updated successfully, but these errors were encountered: