GitOps 流水线. Copy the source, paste into the official playground, done. No coordinates — every position is stated relative to something else.
node dev "Developer"
node repo "GitHub" below dev
node ci "Actions" below repo
node reg "Registry" below ci
node k8s "Kubernetes" below reg
edge dev -> repo "push"
edge repo -> ci "trigger"
edge ci -> reg "push image"
edge reg -> k8s "deploy"npx reladraw ci-cd-pipeline.reladraw -o out.svgThe pipeline diagram for your README: push triggers CI, CI pushes an image to a registry, the registry deploys to Kubernetes. Use it to explain delivery flow to non-engineers, or to spot missing stages (where do tests sit? where does approval happen?).
node test "Tests" below ci and rewire: edge repo -> ci, edge ci -> test, edge test -> reg.node approval "Approve" below reg between registry and cluster: edge reg -> approval, edge approval -> k8s "kubectl apply".node prod "Prod cluster" below k8s and edge k8s -> prod "promote".Every stage is a node, every hand-off is an edge, ordered top to bottom in execution order. This template covers the standard push → build → registry → deploy path and renders in one paste.
Add a branch-protection node: node checks 'PR checks' right of repo with edge repo -> checks. Keep the main path linear — reviewers read top-to-bottom pipelines fastest.
Add a labeled back edge: edge k8s -> reg "rollback: retag" from: left to: left. An explicit back edge is clearer than a note in the caption.