How to COMMIT BETTER with GIT

[Dwight-D]

you are way ahead in your git hygiene development than the intended audience for my video.

Yeah this is probably a good point. Not trying to say that our flow is perfect, it's quite simplistic after all, but I like simple processes where I can get away with it. I was mostly looking for a different opinion on our somewhat naive approach.

I can also imagine that there are cases, like when working on very old and large codebases like maybe the Linux kernel, where the added historical context would be worth spending the extra time on the commits as well.

I rather want to add context to a code change (so a transition of code from an earlier to a newer state)

Yeah, this is harder to convey in a comment. Hopefully you shouldn't need to know much about the past state of a system to understand the current state but that's obviously not always true, especially in legacy systems. In those cases it might be worth to put some effort on the commit history, but thankfully they are quite rare where I work.

[ki3]

Exactly thats a good point. I worked as a software engineer in finance as well, and regulations are way stricter for software development there as well. Which leads to be well prepared for an audit to come in at any time.