A Git graph visualises the branching and merging history of a version-controlled project. Each commit appears as a dot on a branch line; branches diverge when work splits into parallel streams and converge when work is merged back together.

Although Git graphs originate in software development, the same visual structure works for any project that involves branching drafts, review rounds, and final merges — a book edited by multiple people, a newsletter with parallel content streams, or a website with a staging environment.

gitGraph
    commit id: "Initial site setup"
    branch drafts
    checkout drafts
    commit id: "Draft: Summer recipes"
    commit id: "Draft: Italy travel guide"
    checkout main
    branch review
    checkout review
    merge drafts id: "Review pass"
    commit id: "Edits applied"
    checkout main
    merge review id: "Publish summer issue"
    commit id: "Share on social media"
    branch autumn-content
    checkout autumn-content
    commit id: "Draft: Autumn baking"
    commit id: "Draft: Halloween ideas"

The graph makes it clear which content is in draft, which is under review, and what has been published — without any prose explanation needed.