That’s actually not what revert does. Revert doesn’t “take you back to” that commit and pretend that subsequent commits didn’t happen. It applies a logical negation of a single commit – and that commit alone – leaving subsequent commits in place. Let’s say you have some initial commit of some file – let’s call it … Read more
By default git revert refuses to revert a merge commit as what that actually means is ambiguous. I presume that your HEAD is in fact a merge commit. If you want to revert the merge commit, you have to specify which parent of the merge you want to consider to be the main trunk, i.e. … Read more
You can run these two commands: # Revert changes to modified files. git reset –hard # Remove all untracked files and directories. # ‘-f’ is force, ‘-d’ is remove directories. git clean -fd
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
First, it’s always worth noting that git reset –hard is a potentially dangerous command, since it throws away all your uncommitted changes. For safety, you should always check that the output of git status is clean (that is, empty) before using it. Initially you say the following: So I know that Git tracks changes I … Read more
Identify the hash of the commit, using git log, then use git revert <commit> to create a new commit that removes these changes. In a way, git revert is the converse of git cherry-pick — the latter applies the patch to a branch that’s missing it, the former removes it from a branch that has … 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
Expanding what I wrote in a comment The general rule is that you should not rewrite (change) history that you have published, because somebody might have based their work on it. If you rewrite (change) history, you would make problems with merging their changes and with updating for them. So the solution is to create … Read more
You have to “revert the revert”. Depending on you how did the original revert, it may not be as easy as it sounds. Look at the official document on this topic. —o—o—o—M—x—x—W—x—Y / —A—B——————-C—D to allow: —o—o—o—M—x—x——-x——-* / / —A—B——————-C—D But does it all work? Sure it does. You can revert a merge, and from … Read more
Expanding what I wrote in a comment The general rule is that you should not rewrite (change) history that you have published, because somebody might have based their work on it. If you rewrite (change) history, you would make problems with merging their changes and with updating for them. So the solution is to create … Read more