Git graphs: commits on their branches, each commit fed by its parents --
so a merge has two inputs and a branch point two outputs.
A commit Mermaid named itself is announced by its message or its place in
the history rather than by the generated hash, which changes every time the
diagram is drawn.
Git graphs: commits on their branches, each commit fed by its parents -- so a merge has two inputs and a branch point two outputs.
A commit Mermaid named itself is announced by its message or its place in the history rather than by the generated hash, which changes every time the diagram is drawn.