Why would local “remotes/origin/master” be out of sync with the actual remote branch?
Clash Royale CLAN TAG#URR8PPP
Why would local “remotes/origin/master” be out of sync with the actual remote branch?
I am wondering, if you do this:
git fetch origin master;
and the above command succeeds - under what circumstances would the branch "remotes/origin/master" ever be out of sync with the actual remote branch (on Github)?
"remotes/origin/master"
From my observations, it appears that on occasion "remotes/origin/master" sees local changes that are NOT on the actual remote branch on Github. Which is very weird and I cannot explain it.
"remotes/origin/master"
I do create branches like this locally:
git fetch origin master;
git branch --no-track "foo" "remotes/origin/master";
git checkout "foo";
and then when I update foo, it seems like sometimes remotes/origin/master reflects the changes made to foo, which is mfing weird.
foo
remotes/origin/master
foo
git show remotes/origin/master
Do you know how to reproduce this?
– dvaergiller
Aug 6 at 11:05
I forget how to reproduce it, let me think about it
– Alexander Mills
Aug 7 at 3:09
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
When you say that remotes/origin/master reflects local changes, what command output shows those changes? Do you mean
git show remotes/origin/master? Are you using a git UI client like the Github app or Tower?– Chris Middleton
Aug 4 at 22:51