You can do this via revert, which will create another commit but with the reverted changes of the unwanted commit.įirst, use git log to bring up your previous commits. However, you want to revert a change done in C2 without deleting C3. Here, you have three distinctive commits. Let’s take a look at the commit flow below: C1 -> C2 -> C3 You want to revert a commit without deleting things in between. Use the following git command to achieve this: git reset -hard HEAD 😐 5. You just want a clean start on the current branch you’re on.
#Git undo commit pushed code
You can discard the change by typing 'y' for ‘yes’, or keep the changes by typing n for ‘no’.Īnd that’s basically it for keeping/deleting certain chunks or blocks of code in git. You get to chose which block of changes you want to keep or discard. This will take us into an interactive mode where git will go through every chunk of change that’s occurred in the file. You can also write it in longhand with -patch instead of -p. Here is how you can do it: git checkout -p index.js One thing is for sure - you don’t want to revert the entire file back to its original state. There are parts of the code you want to keep, while other parts you want to discard. Here is how you do it: git checkout HEAD accidentallydeletedfilename.js 🤔 3.
You’ve deleted a file in git but want it back. What do you do? Use the following command: git checkout HEAD targetfilename.js 😲 2. You’ve saved something but accidentally also included changes in a file you didn’t want to include. Discard all your local changes in a particular file Here are 10 ways you can undo your GIT mistakes. The point is that you’re not supposed to be making changes to the past once a change has been committed.īut accidents and unintended acts of GIT commits happen. In part, it’s because GIT is version control.
GIT is fantastic when things go as planned - but not so much when it comes to undoing whatever mistake it is you made. We’ve all done it - deleted a file we shouldn’t have, merged things that aren’t supposed to be on the main branch, accidentally pushed up sensitive information, committing to the wrong branch…
0 kommentar(er)
