Concurrency Groups
ELI5 — The Vibe Check
Concurrency Groups prevent CI chaos when you push 5 commits in a row. Instead of running 5 deploys, it cancels the old ones and runs only the latest. It's like a smart queue that says 'why finish cooking the old order when the customer just changed their mind?'
Real Talk
Concurrency groups in GitHub Actions ensure only one workflow run per group key executes at a time. The cancel-in-progress option cancels queued or in-progress runs when a new one starts. Commonly used to prevent parallel deploys to the same environment.
Show Me The Code
concurrency:
group: deploy-${{ github.ref }}
cancel-in-progress: true
When You'll Hear This
"Concurrency groups prevent two deploys to production at the same time." / "We cancel in-progress CI runs when a new push arrives — saves runner minutes."
Related Terms
Deployment Protection Rules
Deployment Protection Rules are the bouncers at your production club.
GitHub Actions
GitHub Actions is CI/CD built right into GitHub. Push code, run tests, deploy — all from YAML files in your repo. No separate CI server needed.
Merge Queue
Two PRs both pass CI separately. Both merge. Main is now broken.