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
In mermaid, tagging can only be done as part of commit. This creates an awkward syntax forcing tagging to happen on a non-release branch (e.g., dev or feature branch) when in reality most tag on the release or default branch (e.g., main)
Example
Desired syntax:
gitGraph
commit
commit
branch dev
commit
commit id: "abcdef"
checkout main
merge dev
tag "v1.0.0" %% optionally you may add id: "abcdef"
Expected Output
Similar to this, but ideally the tag should be placed on the merge node (open circle).
gitGraph
commit
commit
branch dev
commit
commit id: "abcdef" tag: "v1.0.0"
checkout main
merge dev
Loading
Screenshots
No response
The text was updated successfully, but these errors were encountered:
This is already accomodated using merge tags (#3361)
gitGraph
commit
commit
branch dev
commit
commit id: "abcdef"
checkout main
merge dev tag: "v1.0.0"
gitGraph
commit
commit
branch dev
commit
commit id: "abcdef"
checkout main
merge dev tag: "v1.0.0"
Loading
This solves my use case, but having tag as a declarative action might still be useful for other use cases. Closing... Others should request to reopen with their use cases.
Proposal
In git, you can tag the HEAD (current commit).
In mermaid, tagging can only be done as part of
commit
. This creates an awkward syntax forcing tagging to happen on a non-release branch (e.g., dev or feature branch) when in reality most tag on the release or default branch (e.g., main)Example
Desired syntax:
Expected Output
Similar to this, but ideally the tag should be placed on the merge node (open circle).
Screenshots
No response
The text was updated successfully, but these errors were encountered: