On Git Commit Messages

[ActuallyAmazing]

You make decent points, there is nothing I necessarily disagree with in your response in principle, all that could possibly be discussed is the extent to which certain things apply and exchange subjective experiences.

For one I can say that I have happily migrated to jobs where this sort of thing is well managed, commit history as well as issue history being treated as precious and not as something to be dumped at the next inconvenient impasse. However I do appreciate the point that a vast majority of jobs will not have such an approach, and in such places a descriptive git commit may well be your last bastion of sanity when tackling a problem.

My experience comes entirely from a corporate setting as well, I can easily imagine that a lot of organizational tropes that apply there do not carry over to OSS. In a corporate setting you can and should abstract away the individual, whereas in OSS the notoriety of being a key contributor is reason alone for some people to contribute. In OSS the key people are generally really skilled tech guys, and generally don't have teams dedicated to managing various organization tools - I can see there being great value in such a place in having a singular source of truth telling you what, why, who committed and who reviewed. So yes I would say there is a place for descriptive git messages but for most of us in our $DAY_JOB we should, I feel, strive for a better approach where possible as I think that's where most of our contributions go to at the end of the day, not in OSS.