4 ms·
Sure but that's not really helpful, the only thing it does is avoid breaking history visualisation tools which tend to deal very badly with "wide" histories. F
by masklinn 5y ago
Sure but that's not really helpful, the only thing it does is avoid breaking history visualisation tools which tend to deal very badly with "wide" histories.
For instance one of the biggest annoyances with git is it's a pain in the ass to find the the merge of a commit into the mainline (aka the next child with more than one ancestor… probably), which can make it difficult to go back from a commit to a PR unless it was a single-commit pull request.
- Hello71 5y agohttps://github.com/mhagger/git-when-merged https://github.com/mhagger/git-when-merged edit: also https://stackoverflow.com/questions/8475448/find-merge-commit-which-include-a-specific-commit https://stackoverflow.com/questions/8475448/find-merge-commi..., and also github shows this (but only for github PRs, not other merges)
- nemetroid 5y ago> Sure but that's not really helpful, the only thing it does It encodes the necessary information in the commit graph, without introducing a completely new concept (commit groups). It’s true that Git doesn’t give you the tooling to get that information out of the box, though.
- masklinn 5y ago> It encodes the necessary information in the commit graph A bog-standard merge already does that.