I’ve never used Mercurial, but a simple one based on the explanations and my experience with Git:
Locating the branch a commit originated from.
If a git branch has been merged into (or rebased on) main or another branch, there’s no way to tell which commit came from which branch. But sometimes I’d really like that information to figure out what prompted a certain change. Without it, I need to use external tools like a ticketing system and hope the other developers added in the necessary information.
That seems to be the opposite of useful if a commit is initially pushed to a development branch, which is relatively standard practice; now you’re polluting the tree with data that’s purposefully ephemeral, and even potentially leaking internal information.
Also, I’d argue that such deep details do belong in another tool, rather than asking the source control tool perform triple duty by being a CR and issue tracker as well.
I’ve never used Mercurial, but a simple one based on the explanations and my experience with Git:
Locating the branch a commit originated from. If a git branch has been merged into (or rebased on) main or another branch, there’s no way to tell which commit came from which branch. But sometimes I’d really like that information to figure out what prompted a certain change. Without it, I need to use external tools like a ticketing system and hope the other developers added in the necessary information.
That seems to be the opposite of useful if a commit is initially pushed to a development branch, which is relatively standard practice; now you’re polluting the tree with data that’s purposefully ephemeral, and even potentially leaking internal information.
Also, I’d argue that such deep details do belong in another tool, rather than asking the source control tool perform triple duty by being a CR and issue tracker as well.