Can I do the following in a simpler way?
git checkout origin/master
git branch -D master
git branch master
git checkout master
-
Sometimes, this can be done without touching the working tree: stackoverflow.com/a/12343727/586086– Andrew MaoSep 8, 2014 at 19:08
-
8Please update your accepted answer: @KindDragon’s answer is correcter and shorter.– Robert SiemerJan 8, 2016 at 12:17
Add a comment
|
4 Answers
Git supports this command:
git checkout -B master origin/master
Check out the origin/master branch and then reset master branch there.
UPDATE:
Or you can use new switch command for that
git switch -C master origin/master
answered Aug 24, 2014 at 19:30
-
6
-
3save four keystrokes -- you don't need the quotes. Just: git checkout -B master origin/master Mar 24, 2016 at 2:29
-
let's says I commited 2 things, the first one is a merge with branch and the second one is regular. What happens to the merge if I go back to the origin/master?– utdevDec 22, 2016 at 15:05
-
1don't you have to
git fetch origin masterbefore to be sureorigin/masteris updated? Mar 29, 2017 at 16:22 -
As KindDragon's answer mentions, you can recreate master directly at origin/master with:
git checkout -B master origin/master
The git checkout man page mentions:
If -B is given, <new_branch> is created if it doesn’t exist; otherwise, it is reset. This is the transactional equivalent of
$ git branch -f <branch> [<start point>]
$ git checkout <branch>
Since Git 2.23+ (August 2019), since git checkout is too confusing, the new (still experimental) command is git switch:
git switch -C master origin/master
That is:
-C <new-branch> --force-create <new-branch>Similar to
--createexcept that if<new-branch>already exists, it will be reset to<start-point>.
This is a convenient shortcut for:$ git branch -f <new-branch> $ git switch <new-branch>
Originally suggested:
Something like:
$ git checkout master
# remember where the master was referencing to
$ git branch previous_master
# Reset master back to origin/master
$ git reset --hard origin/master
with step 2 being optional.
-
1
-
Thank you VonC, I have updated to accept @KindDragon's answer as dear of you suggested. The technique is always advancing. It's already 10 YEARS!! Love you guys!! ^_^– LenikJul 22, 2020 at 12:17
-
@XièJìléi No problem, good choice. Mine adds more details to KindDragon's.– VonCJul 22, 2020 at 12:33
I think even VonC's answer has complexity compared to this option:
git update-ref refs/heads/master origin/master
git reset --hard master
git automatically logs every value of a ref (through the reflog). So after you run that command, then master@{1} refers to the previous value of master.
VonC's answer is correct, but it wastes time checkout out the old value of master into the filesystem.
If you care about orphaned objects in the repo, then you can run git gc
answered Jan 23, 2013 at 20:48
-
1
-
-
@yourfriendzak, I forgot about taking into account that you might already have master checked out before updating master. I have updated the answer to be one that should work even in that case as well. Aug 22, 2013 at 19:02
-
This works even if you're not on master (like a detached HEAD state that is actually pointing to the tip origin/master). Then, you can checkout master without having to flip old files through the repo. Great! Jul 25, 2014 at 19:26
If you are already on master you can do the following:
git reset --hard origin/master
It will point the local master branch to the remote origin/master and discard any modifications in the working dir.
-
2And will delete files! If you have created/edited files, and have run a "git add" on them, this command will delete them. Be warned.– CheesoNov 11, 2015 at 15:30
-