How do I reset my local branch to be just like the branch on the remote repository?
I tried:
git reset --hard HEAD
But git status claims I have modified files:
On branch master
Changes to be committed:
(use "git reset HEAD <file>..." to unstage)
modified: java/com/mycompany/TestContacts.java
modified: java/com/mycompany/TestParser.java
Setting your branch to exactly match the remote branch can be done in two steps:
git fetch origin
git reset --hard origin/master
If you want to save your current branch's state before doing this (just in case), you can do:
git commit -a -m "Saving my work, just in case"
git branch my-saved-work
Now your work is saved on the branch "my-saved-work" in case you decide you want it back (or want to look at it later or diff it against your updated branch).
Note that the first example assumes that the remote repo's name is "origin" and that the branch named "master" in the remote repo matches the currently checked-out branch in your local repo.
BTW, this situation that you're in looks an awful lot like a common case where a push has been done into the currently checked out branch of a non-bare repository. Did you recently push into your local repo? If not, then no worries -- something else must have caused these files to unexpectedly end up modified. Otherwise, you should be aware that it's not recommended to push into a non-bare repository (and not into the currently checked-out branch, in particular).
git reset FETCH_HEAD --hard instead, as well, that's the same meaning. –
Alegre ticket1066_super_new_feature and I want to reset uat_stable to origin/uat_stable without first doing git checkout uat_stable. If there is, would you consider adding this to the answer? –
Benzine git reset FETCH_HEAD --hard because there's no work tree? –
Megaron git reflog to find it and git cherry-pick $hash to restore it to the branch. –
Gesticulative git reset --hard leaves file modifications in the work tree. I can't find any evidence that pushing to a non-bare repo could cause the behavior in the OP. –
Tailorbird master but some-new-feature? Is it git fetch origin` git reset --hard origin/some-new-feature ? –
Hufuf fatal: ambiguous argument 'origin/master': unknown revision or path not in the working tree. See #38981970 –
Maddy git fetch origin ? origin being already set in git reset --hard origin/master, what would it change if I don't run git fetch origin ? –
Fowler git clean first. Run git clean -n to see what would happen (i.e. which files would be removed), and git clean -f to actually remove them. –
Crossbench git fetch origin before you reset to the remote, then your local copy of the remote repository will not necessarily have all of the latest changes. Git doesn't automatically pull updates from remotes. I'll just add that if you don't specify a branch name it will reset the current branch to the tracking branch, i.e., git reset --hard origin will reset to origin/master if your current branch is tracking origin/master. The same is true for any other branch tracking a remote branch. Might be safer for new users. –
Keare git fetch origin and git reset --hard origin/master and now i have 1200/26000 commits up/down and 92 local changes. how can that be? –
Planar fetch makes sure you have the latest from the remote, otherwise you'll just reset to whatever commit you had locally, which may not be the actual latest commit if others have pushed commits to the remote. –
Microprint git stash like the other answers mentioned below. –
Turgot git stash will not save the branch's state in a way that will survive a git reset. git stash will only save the uncommitted content in the working tree. Creating a copy of the branch will safely save the entire branch's state, such that it can be restored after the git reset, if needed. –
Genni git stash will not lose the commits after a git reset as git stash list can show the commit's hash and you can use git reset --hard <commit's hash> to return and apply the stash. –
Turgot git clean to remove any untracked files –
Riant git reset --hard "@{u}" or git reset --hard ORIG_HEAD. Both do the same thing. The latter one is mentioned on the official git documentation git-scm.com/docs/git-reset#Documentation/… –
Null @{u} works consistently. ORIG_HEAD only works after the specific case of [fetch + merge/rebase]. It wouldn't work if you last moved @{u} via push or fetch, for instance. "ORIG_HEAD is created by commands that move your HEAD in a drastic way (git am, git merge, git rebase, git reset), to record the position of the HEAD before their operation, so that you can easily change the tip of the branch back to the state before you ran them." source –
Metaphrast I needed to do (the solution in the accepted answer):
git fetch origin
git reset --hard origin/master
Followed by:
git clean -f
To see what files will be removed (without actually removing them):
git clean -n -f
git clean -d -f if there are untracked directories present. –
Raptor git clean -fdx –
Inane git clean -f was the essential piece I needed. Thanks! –
Wystand git status still reports a list of modified files. –
Spirillum git clean -nxdf –
Creeps git clean -fdx Stay alert! Untracked directories will be gone❗😉 –
Penicillate First, use git reset to reset to the previously fetched HEAD of the corresponding upstream branch:
git reset --hard @{u}
The advantage of specifying @{u} or its verbose form @{upstream} is that the name of the remote repo and branch don't have to be explicitly specified. On Windows or with PowerShell, specify "@{u}" (with double quotes).
Next, as needed, use git clean to remove untracked files, optionally also with -x:
git clean -df
Finally, as needed, get the latest changes:
git pull
origin/master –
Limpid @{upstream} is very handy and can be used in aliases: alias resetthisbranch="git reset --hard @{upstream}" –
Santiagosantillan @{u} what difference it will make? –
Parshall git reset --hard requires a commit, else it wouldn't know what to reset you to. @{u} points to a specific commit – the head of the tracked branch, from when you last did a git fetch. –
Endblown git reset --hard though it will not reset to remote branch –
Parshall git reset --hard "@{u}"). Took me a while to figure that out. –
Acentric git reset --hard HEAD actually only resets to the last committed state. In this case HEAD refers to the HEAD of your branch.
If you have several commits, this won't work..
What you probably want to do, is reset to the head of origin or whatever you remote repository is called. I'd probably just do something like
git reset --hard origin/HEAD
Be careful though. Hard resets cannot easily be undone. It is better to do as Dan suggests, and branch off a copy of your changes before resetting.
All of the above suggests are right, but often to really reset your project, you also need to remove even files that are in your .gitignore.
To get the moral equivalent of erasing your project directory and re-cloning from the remote is:
git fetch
git reset --hard
git clean -x -d -f
Warning: git clean -x -d -f is irreversible and you may lose files and data (e.g. things you have ignored using .gitignore).
git clean -xdf that is equal to git clean -x -d -f. –
Wretched Use the commands below. These commands will remove all untracked files from local git too
git fetch origin
git reset --hard origin/master
git clean -d -f
git clean -d -f we'll still had some things of the old branch in local directory. Thanks man. –
Jungjungfrau The question mixes two issues here:
git status says nothing to commit, working directory clean.The one-stop-answer is:
git fetch --prune (optional) Updates the local snapshot of the remote repo. Further commands are local only.git reset --hard @{upstream}Puts the local branch pointer to where the snapshot of the remote is, as well as set the index and the working directory to the files of that commit.git clean -d --force Removes untracked files and directories which hinder git to say “working directory clean”.@{upstream} syntax requires upstream to be set which happens by default if you git checkout <branchname>. – Otherwise replace it with origin/<branchname>. –
Selfconfessed -x to git clean to remove everything not in the commit (i.e. even files ignored with the .gitignore mechanism). –
Selfconfessed Provided that the remote repository is origin, and that you're interested in branch_name:
git fetch origin
git reset --hard origin/<branch_name>
Also, you go for reset the current branch of origin to HEAD.
git fetch origin
git reset --hard origin/HEAD
How it works:
git fetch origin downloads the latest from remote without trying to merge or rebase anything.
Then the git reset resets the <branch_name> branch to what you just fetched. The --hard option changes all the files in your working tree to match the files in origin/branch_name.
origin/HEAD here and I don't think it's correct –
Ashelman This is something I face regularly, & I've generalised the script Wolfgang provided above to work with any branch
I also added an "are you sure" prompt, & some feedback output
#!/bin/bash
# reset the current repository
# WF 2012-10-15
# AT 2012-11-09
# see https://mcmap.net/q/11478/-reset-local-repository-branch-to-be-just-like-remote-repository-head
timestamp=`date "+%Y-%m-%d-%H_%M_%S"`
branchname=`git rev-parse --symbolic-full-name --abbrev-ref HEAD`
read -p "Reset branch $branchname to origin (y/n)? "
[ "$REPLY" != "y" ] ||
echo "about to auto-commit any changes"
git commit -a -m "auto commit at $timestamp"
if [ $? -eq 0 ]
then
echo "Creating backup auto-save branch: auto-save-$branchname-at-$timestamp"
git branch "auto-save-$branchname-at-$timestamp"
fi
echo "now resetting to origin/$branchname"
git fetch origin
git reset --hard origin/$branchname
[ "$REPLY" != "y" ] || will only skip the next line echo "about to auto-commit any changes" and continue running the rest of the script. The line should read something like [[ "$REPLY" != "y" ]] && { echo "Exiting branch reset"; exit; }. –
Klopstock You can fetch the origin and reset to solve the problem
git fetch origin
git reset --hard origin/main
You can save your changes before doing the reset like below,
git stash
And after resetting, if you want that changes back, you can simply run,
git stash apply
I did:
git branch -D master
git checkout master
to totally reset branch
note, you should checkout to another branch to be able to delete required branch
Here is a script that automates what the most popular answer suggests ... See https://mcmap.net/q/11478/-reset-local-repository-branch-to-be-just-like-remote-repository-head for an improved version that supports branches
#!/bin/bash
# reset the current repository
# WF 2012-10-15
# see https://mcmap.net/q/11478/-reset-local-repository-branch-to-be-just-like-remote-repository-head
timestamp=`date "+%Y-%m-%d-%H_%M_%S"`
git commit -a -m "auto commit at $timestamp"
if [ $? -eq 0 ]
then
git branch "auto-save-at-$timestamp"
fi
git fetch origin
git reset --hard origin/master
The answer
git clean -d -f
was underrated (-d to remove directories). Thanks!
git clean -xdf. This will delete any and all files that git is not aware of, and will make your folder match what is in git's object list exactly. Note that you can add -n (e.g. git clean -nxdf) to perform a "what-if" and it will tell you what it will delete without actually doing anything. (git clean) –
Pyknic 2023 simple solution :
git fetch
git reset --hard @{u}
Reseting to origin/HEAD won't always work as it's not necessarily the latest commit of your current branch.
If you had a problem as me, that you have already committed some changes, but now, for any reason you want to get rid of it, the quickest way is to use git reset like this:
git reset --hard HEAD~2
I had 2 not needed commits, hence the number 2. You can change it to your own number of commits to reset.
So answering your question - if you're 5 commits ahead of remote repository HEAD, you should run this command:
git reset --hard HEAD~5
Notice that you will lose the changes you've made, so be careful!
Previous answers assume that the branch to be reset is the current branch (checked out). In comments, OP hap497 clarified that the branch is indeed checked out, but this is not explicitly required by the original question. Since there is at least one "duplicate" question, Reset branch completely to repository state, which does not assume that the branch is checked out, here's an alternative:
If branch "mybranch" is not currently checked out, to reset it to remote branch "myremote/mybranch"'s head, you can use this low-level command:
git update-ref refs/heads/mybranch myremote/mybranch
This method leaves the checked out branch as it is, and the working tree untouched. It simply moves mybranch's head to another commit, whatever is given as the second argument. This is especially helpful if multiple branches need to be updated to new remote heads.
Use caution when doing this, though, and use gitk or a similar tool to double check source and destination. If you accidentally do this on the current branch (and git will not keep you from this), you may become confused, because the new branch content does not match the working tree, which did not change (to fix, update the branch again, to where it was before).
This is what I use often:
git fetch upstream develop;
git reset --hard upstream/develop;
git clean -d --force;
Note that it is good practice not to make changes to your local master/develop branch, but instead checkout to another branch for any change, with the branch name prepended by the type of change, e.g. feat/, chore/, fix/, etc. Thus you only need to pull changes, not push any changes from master. Same thing for other branches that others contribute to. So the above should only be used if you have happened to commit changes to a branch that others have committed to, and need to reset. Otherwise in future avoid pushing to a branch that others push to, instead checkout and push to the said branch via the checked out branch.
If you want to reset your local branch to the latest commit in the upstream branch, what works for me so far is:
Check your remotes, make sure your upstream and origin are what you expect, if not as expected then use git remote add upstream <insert URL>, e.g. of the original GitHub repo that you forked from, and/or git remote add origin <insert URL of the forked GitHub repo>.
git remote --verbose
git checkout develop;
git commit -m "Saving work.";
git branch saved-work;
git fetch upstream develop;
git reset --hard upstream/develop;
git clean -d --force
On GitHub, you can also checkout the branch with the same name as the local one, in order to save the work there, although this isn't necessary if origin develop has the same changes as the local saved-work branch. I'm using the develop branch as an example, but it can be any existing branch name.
git add .
git commit -m "Reset to upstream/develop"
git push --force origin develop
Then if you need to merge these changes with another branch while where there are any conflicts, preserving the changes in develop, use:
git merge -s recursive -X theirs develop
While use
git merge -s recursive -X ours develop
to preserve branch_name's conflicting changes. Otherwise use a mergetool with git mergetool.
With all the changes together:
git commit -m "Saving work.";
git branch saved-work;
git checkout develop;
git fetch upstream develop;
git reset --hard upstream/develop;
git clean -d --force;
git add .;
git commit -m "Reset to upstream/develop";
git push --force origin develop;
git checkout branch_name;
git merge develop;
Note that instead of upstream/develop you could use a commit hash, other branch name, etc. Use a CLI tool such as Oh My Zsh to check that your branch is green indicating that there is nothing to commit and the working directory is clean (which is confirmed or also verifiable by git status). Note that this may actually add commits compared to upstream develop if there is anything automatically added by a commit, e.g. UML diagrams, license headers, etc., so in that case, you could then pull the changes on origin develop to upstream develop, if needed.
Only 3 commands will make it work
git fetch origin
git reset --hard origin/HEAD
git clean -f
The top rated answer here did not reset my local code as expected.
Instead:
check the name of your default remote branch (this is not a git thing so check in GitHub) then replace main or master in step 4 below with this
save current stuff
git stash -u
update from remote
git fetch origin
reset to remote default branch (but see step 1 above)
git reset --hard origin/main
If you want to go back to the HEAD state for both the working directory and the index, then you should git reset --hard HEAD, rather than to HEAD^. (This may have been a typo, just like the single versus double dash for --hard.)
As for your specific question as to why those files appear in the status as modified, it looks like perhaps you did a soft reset instead of a hard reset. This will cause the files that were changed in the HEAD commit to appear as if they were staged, which is likely what you are seeing here.
No amount of reset and cleaning seemed to have any effect on untracked and modified files in my local git repo (I tried all the options above). My only solution to this was to rm the local repo and re-clone it from the remote.
Fortunately I didn't have any other branches I cared about.
First, check with git status if you have any local changes. If yes, stash them.
Then execute:
git fetch
git reset --hard @{push}
It will reset the current local branch to the same remote branch which would be used for git push.
This is especially useful when git config push.default current is configured. For example, when your branch is abc and remote is origin, it will reset it to origin/abc.
Please see Git revisions for more details about @{push}
@{push} –
Jockstrap The only solution that works in all cases that I've seen is to delete and reclone. Maybe there's another way, but obviously this way leaves no chance of old state being left there, so I prefer it. Bash one-liner you can set as a macro if you often mess things up in git:
REPO_PATH=$(pwd) && GIT_URL=$(git config --get remote.origin.url) && cd .. && rm -rf $REPO_PATH && git clone --recursive $GIT_URL $REPO_PATH && cd $REPO_PATH
* assumes your .git files aren't corrupt
Have you forgotten to create a feature-branch and have committed directly on master by mistake?
You can create the feature branch now and set master back without affecting the worktree (local filesystem) to avoid triggering builds, tests and trouble with file-locks:
git checkout -b feature-branch
git branch -f master origin/master
git stashgit stash applygit pullgit fetch origin
git checkout main
git reset --hard origin/main
# Local `master` branch is now up to date with remote `main`
If you don't mind saving your local changes, yet still want to update your repository to match origin/HEAD, you can simply stash your local changes and then pull:
git stash
git pull
© 2022 - 2024 — McMap. All rights reserved.
git statusyour second commandgit reset --hard HEADfailed. You didn’t paste it’s output, though. → Incomplete question. – Selfconfessedgit statussaysnothing to commit, working directory clean. – Please specify! – Selfconfessedrm -fr ./repo; git clone repo. best way i've found – Hibernategit reset --hard origin/masterwhen it should have beengit reset --hard origin/main. – Lexinegit reset --hard FETCH_HEADworked for me. I hadn't pushed after rebase. – Dabney