FlowchartCI/CD pipelineMedium

GitHub Actions release pipeline

CI pipeline running lint, test, build, tag, and publish through GitHub Actions jobs.

What this diagram shows

Step 01

Parallel gates

Lint and test run side by side the moment a push lands on main.

Step 02

Build and tag

Artifacts are built once both gates pass, then a release tag is cut.

Step 03

Publish and notify

The package is published and a Slack notification closes the loop.

About flowchart diagrams

Flowcharts map out a process as boxes and arrows. They work well when you need to explain how a decision, workflow, or pipeline moves from one step to the next.

This template is written in Mermaid — plain text you can edit, version in git, and regenerate the image from any time.

View Mermaid sourcePlain-text diagram syntax — copy or edit directly.

diagram.mmd

1graph LR
2  Push[Push to main] --> Lint[Lint]
3  Push --> Test[Test]
4  Lint --> Build[Build artifacts]
5  Test --> Build
6  Build --> Tag[Create release tag]
7  Tag --> Publish[Publish package]
8  Publish --> Notify[Notify Slack]

Related templates

More templates that cover similar workflows.

FLOWCHART

Memphis

Staged deploy with approval gate

Promote a build through staging, smoke tests, manual approval, and production rollout.

CI/CD pipelineMedium9 nodes

FLOWCHART

Atlas

Microservices overview

High-level view of a microservices system with gateway, services, and shared datastores.

System architectureMedium8 nodes

FLOWCHART

Slate

Webhook delivery with retry

Outbound webhook pipeline with signing, retry on failure, and dead-letter fallback.

API workflowMedium8 nodes

FLOWCHART

Obsidian

Retry with exponential backoff

Retry strategy using exponential backoff with jitter and a hard cap on attempts.

Retry & error handlingMedium6 nodes