> You could use branches / tags for this purpose. Yeah that's what I meant by save them. > Reverts are not too bad becuase they are pretty meaningful. I was

> You could use branches / tags for this purpose. Yeah that's what I meant by save them. > Reverts are not too bad becuase they are pretty meaningful. I was responding to: "I still revert rather than reset and don't force push". Say you are working privately on a branch, saving your work, etc. You realize you made a silly error, and need to undo a commit. Creating a revert commit here is a pretty serious error of git organization imo. Typically you do not want to save this work... it is just your private mess as you were working through the problem, and when you are done and have solved it, you want to save the final result, as clean history, perhaps as multiple commits, perhaps as one. After you have published your work publicly, then yes, you need to do a revert commit if you made a mistake.