Git merge of remote branch reports “Already up-to-date” when there are new remote commits -


we regularly run merge:

git merge origin/feature-branch 

it seems there lag can see commit in feature-branch (using bitbucket) merge command returns already up-to-date.. have wait around 10 minutes after commit run merge. there cache needs cleared latest without waiting?


update:

the solution described below. turns out there wasn't "lag" or cache. guess in past ran git pull in between unsuccessful , successful merge attempts.

solution here run git pull first:

git pull git merge origin/feature-branch 

this blog post sorted me out. had no idea that:

you may not have realised git keeps clone of remote repositories on machine ... origin/master not on github, it’s clone of remote master branch on machine.

thus had git pull update "local" clone of origin/master. merged worked!


Comments

Popular posts from this blog

unity3d - Rotate an object to face an opposite direction -

angular - Is it possible to get native element for formControl? -

javascript - Why jQuery Select box change event is now working? -