Show our branching strategy with feature, release, and hotfix branches
About the framework
The Mermaid Git graph uses main, develop, feature/auth, feature/dashboard, and hotfix/login. Authentication adds OAuth and sessions, while the dashboard adds charts and filters. Each feature branch merges into develop before develop merges into main for the v1.0.0 tag.
The hotfix branch starts from main after that release and adds a token-expiry fix. It merges into main with the v1.0.1 tag, then main merges into develop as Sync hotfix. That final merge makes the patch’s return to ongoing development visible.
Use this example to explain the intended branch sequence. It records illustrative commits and merges, without defining review requirements, CI checks, deployments, or branch-protection settings. Add those annotations if they are part of the release process you need to communicate.
What's included
Git Release Workflow (Gitgraph)
✦ Free preview · Sign in to use
Frequently asked questions
Both feature/auth and feature/dashboard branch from develop and merge back into it before the first tagged release.
After hotfix/login merges into main for v1.0.1, the diagram shows main merging into develop with the label Sync hotfix.
The graph only shows Git history and tags. It includes no deployment step or evidence of a running release.
Free to start. No credit card required.