![]() This method leaves the checked out branch as it is, and the working tree untouched. 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 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: In comments, OP hap497 clarified that the branch is indeed checked out, but this is not explicitly required by the original question. Previous answers assume that the branch to be reset is the current branch (checked out). 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). 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. 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.īTW, 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. 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). 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" Setting your branch to exactly match the remote branch can be done in two steps: git fetch origin
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |