ENGINEERING
Block deploy PR merges in GitHub while error budget is exhausted
When a pull request targets a release branch, it checks the service's remaining SLO budget in Datadog and, if the budget is exhausted, posts a blocking review and a failing…
How it runs
The automated pipeline, trigger to output.
- TriggerPR opened against release branchGitHub
- ActionLook up service remaining budget in DatadogDatadog
- LogicDecide pass or block vs budget floor
- ActionSet failing GitHub status check on the PRGitHub
- OutputPost blocking review with recovery estimateGitHub
What it does
This workflow puts the error budget directly in the pull request workflow. The moment a PR opens against a protected release branch, it looks up the target service's remaining SLO budget and, if the budget is below the safe floor, it blocks the merge with a failing GitHub status check and an explanatory blocking review comment.
When to use it
Use this when deploys happen by merging to a release branch and you enforce branch protection. It stops engineers from merging change into a service that is already out of budget, without requiring anyone to manually check a dashboard.
How it works
- 1A GitHub pull_request event fires when a PR opens or updates against the release branch.
- 2The workflow maps the changed paths to the affected service and queries Datadog for its remaining SLO budget.
- 3A logic step decides pass or block against the configured budget floor.
- 4If blocked, it posts a failing commit status check and a blocking review explaining the freeze.
- 5It comments on the PR with the current budget and recovery estimate so the author knows when to retry.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect DatadogMetrics, traces, log search.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.