MyMapGit Release Workflow (Gitgraph)
A gitgraph diagram showing a feature-branch workflow — develop branch, two feature branches merged to main as v1.0.0, plus a hotfix branch for v1.0.1.
Preview
“Show our branching strategy with feature, release, and hotfix branches”
About the framework
Gitgraph Framework for Release Workflow Documentation
This template applies the Mermaid gitgraph framework to a feature-branch release workflow — the branching strategy used by most engineering teams that practice trunk-based development or GitHub Flow. Gitgraph diagrams are the clearest way to explain branching strategies to new team members, stakeholders, and technical reviewers because they show commits, branches, merges, and tags in the same visual language as a real git history.
The workflow shown here is a production pattern: a `develop` branch receives feature branches (`feature/auth`, `feature/dashboard`) that merge in sequence. When `develop` is stable, it merges to `main` and gets tagged as `v1.0.0`. A critical bug discovered post-release spawns a `hotfix` branch directly from `main`, which merges back to both `main` (as `v1.0.1`) and `develop` to keep the branches in sync.
This template is used in engineering onboarding documents, architecture decision records (ADRs), and team wikis. It answers the question every developer asks when joining a project: 'What's our branching strategy?' Use the AI to model GitFlow, trunk-based development, or a custom branching strategy specific to your team.
What's included
What you get
- Gitgraph with main, develop, feature, and hotfix branches
- Two feature branches: auth and dashboard
- Tagged v1.0.0 release from develop
- Hotfix branch producing v1.0.1 patch
- Hotfix sync back to develop
Git Release Workflow (Gitgraph)
Frequently asked questions
Common questions
Can I model a GitFlow strategy with separate release branches?
Yes. Ask the AI to 'Add a release branch that branches from develop, receives only bug fixes, then merges to main with a version tag.' GitFlow's additional branch types all render correctly in Mermaid gitgraph syntax.
How do I show multiple feature branches being worked on in parallel?
The AI can add as many parallel branches as needed. 'Add three more feature branches: feature/payments, feature/notifications, and feature/settings, all branching from develop at different commit points.' Each branch will appear in its own color.
Can I use this diagram in an engineering onboarding document?
This is one of the most common use cases. Export the diagram and embed it in your engineering wiki or README. Combined with a written explanation of when to create each branch type, it becomes a complete branching strategy reference.
Does this template work for teams using GitHub Actions or CI/CD pipelines?
The gitgraph shows the branching strategy; the CI/CD pipeline is a separate concern. You can use the sequence diagram template to document what happens when each branch type is pushed, and link both diagrams in your engineering documentation.
Git Release Workflow (Gitgraph)
Free to start. No credit card required.