You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ability to add commit messages to commits in a GitGraph.
It's already possible for commits in a GitGraph to be augmented with a custom ID, a type, and a tag.
Users might use the custom ID field to act as a commit message instead. However, although it's not officially documented, there is a tacit assumption that commit IDs in the graph should be unique, else commands like cherry-pick do not work.
Commit messages sometimes need to duplicated. IDs in the graph should be unique, but messages should not.
This was picked up in conversation on issue #4838 where duplication of an ID acting as a message caused an error in the rendering of the graph.
(NB. A similar issue exists but I think it's different: issue #3900 asks for annotations. But this would be more like comments overlaid on top of any aspect of the graph, whether they be commits, branch lines, and merge or cherry-pick arrows. This issue is a syntax request for messages directly integrated into the graph.)
Proposal
Ability to add commit messages to commits in a GitGraph.
It's already possible for commits in a GitGraph to be augmented with a custom ID, a type, and a tag.
Users might use the custom ID field to act as a commit message instead. However, although it's not officially documented, there is a tacit assumption that commit IDs in the graph should be unique, else commands like
cherry-pick
do not work.Commit messages sometimes need to duplicated. IDs in the graph should be unique, but messages should not.
This was picked up in conversation on issue #4838 where duplication of an ID acting as a message caused an error in the rendering of the graph.
(NB. A similar issue exists but I think it's different: issue #3900 asks for annotations. But this would be more like comments overlaid on top of any aspect of the graph, whether they be commits, branch lines, and merge or cherry-pick arrows. This issue is a syntax request for messages directly integrated into the graph.)
Example
By itself:
With custom ID:
With custom IDs, tags, and types:
Screenshots
A rough idea of what this could look like:
Suggestions:
The text was updated successfully, but these errors were encountered: