The commit has been reverted, and no history was lost. Here is the command:Īfter being prompted to enter a commit message, we can now see in our commit history that there is actually a new commit: $ git log -pretty=onelineį68e546ac2ae240f22b2676b5aec499aab27f1ca Revert "Added 'awesome' to text"Ħ76ec97a9cb2cebbb5c77904bbc61ced05b86f52 Added 'awesome' to textħ35c5b43bf4b5b7107a9cc3f6614a3890e2889f6 Initial commitĪs a result of this, the first and third commits represent the exact same project state. This is ideal for published changes because then the true history of the repo is preserved. This command works by undoing changes that were made in the specific commit by creating a new commit and not actually removing any previous commits. Instead, the recommended approach would be to use the revert command. At this point it's highly advised that you do not use something like git reset since you'd be rewriting history.
Git reset all local changes code#
So let's say you committed your code and then pushed it to the remote repository. So if you have uncommitted changes that you want to keep, then this is likely the option you want.
This option works much the same way as git reset -hard, but it only affects the commit history, not your working directory or staging index. The other option you may consider is the -soft option. The stash command saves your working changes (without any commits or changes to the tree), and then stash pop brings them back. To avoid losing any working changes, you can use the stash and stash pop commands: $ git stash $ git reset -hard $ git stash pop This means that by using just this command you'll not only revert to a previous commit, but you'll lose all working changes in the process. This includes the commit history reference pointers, the staging index, and your working directory.
Using the -hard option, everything is reverted back to the specific commit. The reset command has three different options, two of which we'll describe here: The only way to find and recover these unreferenced commits is with git reflog. While this is an effective solution, it's a dangerous one since you're rewriting history and leaving the "deleted" commits unreferenced, or "orphaned". If you haven't yet published your commits to a remote repository, like GitHub, then you can essentially delete previous commits by using the reset command. This is a complicated topic (which is true for many Git topics in general), so make sure you follow the instructions that best suit your needs. In this article I'll show a few ways to revert your commits, depending on your use-case. Whether you accidentally commit changes, or just realized your previous committed code isn't what you wanted, oftentimes you'll need to revert a previous commit in Git. This equally applies to version control tools as well. If I've learned anything in my 15+ years of programming, it's that mistakes are common, and I make a lot of them.
0 kommentar(er)
