Describing your changes to the code base is a difficult task. Especially for younger software developers. With this guide, I want to summarize my learnings over the last couple of years. 1. Atomic Commits - one change per commit I found, that the des...
Markdown supported · ⌘↵ to post
Thank you very much! And great point. I think it‘s much simpler to understand for non native speakers and saves additional chars. Think of added and add.
On the other hand, I like thinking about the commit as a subject, that is adding or fixing something to or in the codebase currently, when viewing the commit later.
But I don‘t think its a great mistake to write in simple past tense, I just stick to the present tense for those two reasons
Divyanshi
Software Engineer - who is learning and sharing new things every now and then, follow along!
Nice and crisp article. Would like to know more on the point number 4, for me it always feels like the commit msg should be written in past tense, what is the thought process behind adding it as present tense?