Find the last commit that affected the given path. As the file isn’t in the HEAD commit, that previous commit must have deleted it. git rev-list -n 1 HEAD — <file_path> Then checkout the version at the commit before, using the caret (^) symbol: git checkout <deleting_commit>^ — <file_path> Or in one command, if $file … Read more
Assuming the hash of the commit you want is c5f567: git checkout c5f567 — file1/to/restore file2/to/restore The git checkout man page gives more information. If you want to revert to the commit before c5f567, append ~1 (where 1 is the number of commits you want to go back, it can be anything): git checkout c5f567~1 … Read more
Let’s start by explaining what a tag in git is A tag is used to label and mark a specific commit in the history. It is usually used to mark release points (eg. v1.0, etc.). Although a tag may appear similar to a branch, a tag, however, does not change. It points directly to a … Read more
These three commands have entirely different purposes. They are not even remotely similar. git revert This command creates a new commit that undoes the changes from a previous commit. This command adds new history to the project (it doesn’t modify existing history). git checkout This command checks-out content from the repository and puts it in … Read more
To keep your current changes You can keep your work stashed away, without commiting it, with git stash. You would than use git stash pop to get it back. Or you can (as carleeto said) git commit it to a separate branch. Checkout by date using rev-parse You can checkout a commit by a specific … Read more
The two commands have the same effect (thanks to Robert Siemer’s answer for pointing it out). The practical difference comes when using a local branch named differently: git checkout -b mybranch origin/abranch will create mybranch and track origin/abranch git checkout –track origin/abranch will only create ‘abranch‘, not a branch with a different name. (That is, … Read more
Try this: git checkout [revision] . where [revision] is the commit hash (for example: 12345678901234567890123456789012345678ab). Don’t forget the . at the end, very important. This will apply changes to the whole tree. You should execute this command in the git project root. If you are in any sub directory, then this command only changes the … Read more
In git version 1.7.9.5 this seems to work to export a single file from a remote git archive –remote=ssh://host/pathto/repo.git HEAD README.md This will cat the contents of the file README.md.
git reset is specifically about updating the index, moving the HEAD. git checkout is about updating the working tree (to the index or the specified tree). It will update the HEAD only if you checkout a branch (if not, you end up with a detached HEAD). (actually, with Git 2.23 Q3 2019, this will be … Read more
Suppose I have a file named path/to/file.txt in my Git repository, and I want to revert changes on it. git checkout path/to/file.txt Now suppose that the file is named master… git checkout master Whoops! That changed branches instead. The — separates the tree you want to check out from the files you want to check … Read more