
Git branching strategy diagram template
Lanes for main, develop, feature, release and hotfix · Commits, merges and version tags · One rule per branch type
Preview and use template →A CI/CD pipeline diagram shows what happens to a change between merge and production, and what stops a bad one. This example runs eight stages from commit to monitoring, then promotes a canary to full rollout or rolls back automatically, with the pipeline rules the team agreed underneath.
No account needed · Opens as your own editable page

Rename the chevrons to match your CI configuration and add real durations. Seeing the time per stage shows where a slow pipeline loses minutes on every merge.
Replace the example error rate and latency limits with thresholds from your monitoring. Automatic rollback only helps if the limits are specific enough for a script to check.
Keep the rules short and testable, such as using the same image in staging and production. Review them whenever an incident shows that a rule was missing or ignored.
Yes. Delete the approval stage and connect the stage before it to the canary release if your team deploys automatically once every check passes.
No. Open the template and edit it in your browser. Your work saves on this device. An account is optional if you want to sync your workspace.
Yes. Use Export in the editor to save a PNG, SVG or PDF, or download an editable .epicdraw backup.