re: How I Write Source Control Commit Messages VIEW POST

re: I try to keep it to one card per commit! I'd like to offer a deeper tip here. It is good practice to keep commits to functional units of work. A ...

First, thanks for sharing @rachelsoderberg ;)

Just came down here to write the same, I consider commits as the good old video game checkpoints.

Every time you hit a "safe place" where you would like to go back in case of something goes wrong, add a commit with a very descriptive message.

Your "future myself" (and code reviewers) will thank you a lot.

Further reading: pauline-vos.nl/atomic-commits/


Love the analogy, I think of it the same way 😀

Code of Conduct Report abuse