3 ms·
Curious that this comes on front page along side the whole Atlassian / Jira debate. One of the major reasons Github does not / cannot do commit messages the wa
by lifeisstillgood 5y ago
Curious that this comes on front page along side the whole Atlassian / Jira debate.
One of the major reasons Github does not / cannot do commit messages the way Linus likes is that the reasons why odd is changed are in and supposed to be in the ticket tracker (where non-coders / committers can view / comment / approve.)
This is not a technical fix that github can make - this is a fundamental split about where the power lies - most companies do not have the final say, the source of truth, in their codebase and consequently their repos.
Linus is on the side of history here. But for those of us coders living in ticket trackers for our daily job, it's a serious culture shock. For non- coders it's an existential threat.
On a separate note, I think there is a space for using hashes to compress tickets and all the ancillary evidence and sign offs, into one artifact, and then reference that in the repo commit. But I just can't see it in my head
- dathinab 5y ago> Linus is on the side of history here. Through not seldom the source of truth is also hidden somewhere in the Linux mailing list. Similar a (insane) high amount of projects on GitHub and in companies will hardly ever use the history besides a last few commits. Sure git blame is a thing, and so is bisect but how often is it used on projects besides large open-source projects?