Communicating workflow with Git graphs

The Git versioning system involves individual commits that modify one or more files on a specific branch. Most development teams work on more than one work item at the same time.

In order to keep code manageable and reduce the odds of shipping code on accident developers use branches for features, fixes, and even long-running software releases needing separate fixes.

This can make git repositories complex to understand without the right graphical tools. Thankfully, Git graphs help with this by allowing you to visualize different branches and how they interact with each other.

In Mermaid, Git graphs work by using commit lines to mark a commit on the current branch, the branch command to create a branch, checkout to switch to a branch, and merge to merge the contents of the target branch to the current branch.

All of this was designed to resemble how developers interact with Git normally, but in practice, it involves remembering which...