To get the most recent tag (example output afterwards): git describe –tags –abbrev=0 # 0.1.0-dev To get the most recent tag, with the number of additional commits on top of the tagged object & more: git describe –tags # 0.1.0-dev-93-g1416689 To get the most recent annotated tag: git describe –abbrev=0
git checkout master # first get back to master git checkout experiment — app.js # then copy the version of app.js # from branch “experiment” See also git how to undo changes of one file? Update August 2019, Git 2.23 With the new git switch and git restore commands, that would be: git switch master … Read more
Originally, I mentioned in 2012 git archive (see Jared Forsyth‘s answer and Robert Knight‘s answer), since git1.7.9.5 (March 2012), Paul Brannan‘s answer: git archive –format=tar –remote=origin HEAD:path/to/directory — filename | tar -O -xf – But: in 2013, that was no longer possible for remote https://github.com URLs. See the old page “Can I archive a repository?“ … Read more
Using Commit Ranges with Git Log When you’re using commit ranges like .. and … with git log, the difference between them is that, for branches A and B, git log A..B will show you all of the commits that B has that A doesn’t have, while git log A…B will show you both the … Read more
The Short Answer As long as you’re doing a fast-forward merge, then you can simply use git fetch <remote> <sourceBranch>:<destinationBranch> Examples: # Merge local branch foo into local branch master, # without having to checkout master first. # Here `.` means to use the local repository as the “remote”: git fetch . foo:master # Merge … Read more
Before answering, let’s add some background, explaining what this HEAD is. First of all what is HEAD? HEAD is simply a reference to the current commit (latest) on the current branch. There can only be a single HEAD at any given time (excluding git worktree). The content of HEAD is stored inside .git/HEAD and it … Read more
If you want to revert changes made to your working copy, do this: git checkout . Or equivalently, for git version >= 2.23: git restore . If you want to revert changes made to the index (i.e., that you have added), do this. Warning this will reset all of your unpushed commits to master!: git … Read more
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
How can I reset or revert a file to a specific revision?
This depends a lot on what you mean by “revert”. Temporarily switch to a different commit If you want to temporarily go back to it, fool around, then come back to where you are, all you have to do is check out the desired commit: # This will detach your HEAD, that is, leave you … Read more