I can never remember that, but the good news is I don’t have to. I’ve always had to look up how you undo the most recent commit: git reset – hard HEAD~1
Maybe I included files that should not have been there, or I forgot to include some changes that should have been in there. In almost every single project that I’ve worked on, I’ve hit a point where I’ve committed some code and then actually wanted to go back and change some things about that commit. Compare and revert changes in bulk, or one at a timeĪll of that is really nice, but that’s not what I wanted to show you.Shows you side by side comparison to see each change.Take a snapshot of the current state of the project.VS Code has some really nice Git integrations that they have well documented. We have tools like Git, which has been around for a while and hopefully you’ve heard of it. If you’ve been in the field a while and that brought up some deeply rooted trauma, I know a great therapist.īut technology has advanced enough that we don’t need to rely on that sort of format. If you need more versions, you keep copy/pasting until you get to “V3”, “V4”, “V_final”, then “V_finalfinal”, and then “_-this-time-for-real-final_version_V7”. The first thing you want to do when you need to modify a file is to copy and paste it, then rename the new file to “V2”. Today I wanna show you some tips in VS Code to prevent that from happening. If you’ve been working in web development for a while, you may run into scenarios where you make some changes or delete some files, and somehow lose work and a lot of time as a result.
0 kommentar(er)
