2 ms·
Higher level tooling doesn't prioritize this. That's an excellent point. It's deep in the DNA of GitHub, unfortunately. I'm always reminded of this contrast:
by bJGVygG7MQVF8c 6y ago
Higher level tooling doesn't prioritize this.
That's an excellent point.
It's deep in the DNA of GitHub, unfortunately. I'm always reminded of this contrast:
> Look, I don’t give two shits about my Git commits. [...]
> From GitHub’s perspective, individual commits become less valuable because the atomic unit is the pull request.
Utter Disregard for Git Commit History
https://zachholman.com/posts/git-commit-history/ https://zachholman.com/posts/git-commit-history/
(The problem with this "unit of change" theorizing is obvious, especially considering GH only recently added a squash-merge feature.)
vs. Torvalds on GitHub PRs:
> Git comes with a nice pull-request generation module, but github instead decided to replace it with their own totally inferior version. As a result, I consider github useless for these kinds of things. It's fine for hosting, but the pull requests and the online commit editing, are just pure garbage.
https://github.com/torvalds/linux/pull/17#issuecomment-5654674 https://github.com/torvalds/linux/pull/17#issuecomment-56546...
- hinkley 6y agoCommit squashing is a scourge. I sometimes go the other way; rewrite my history as a set of independent refactors.