ENGINEERING
Block GitHub PR Merges When SLO Burn Rate Is Hot
On every GitHub pull request, queries the target service's Honeycomb SLO burn rate and posts a pass/fail status check plus a PR comment showing the math.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull request opened or updatedGitHub
- ActionFetch target service SLO burn rate from HoneycombHoneycomb
- LogicCompare 1h/6h burn against fast-burn threshold
- ActionPost burn-rate math as PR commentGitHub
- OutputSet commit status check to pass or failGitHub
What it does
Gates merges on the health of the service the PR touches. When a pull request opens or updates, it pulls the service's current short-window and long-window error-budget burn rate from Honeycomb, compares them to your fast-burn threshold, and writes a GitHub commit status (success or failure). It also drops a PR comment spelling out the budget remaining, the burn multiplier, and the verdict so reviewers see the reasoning inline.
When to use it
Use it when a service has a defined Honeycomb SLO and you want risky changes held back during active budget burn — without asking engineers to check dashboards manually. Pair it with a required-status-check branch rule so a failing gate actually blocks the merge button.
How it works
- 1A pull_request event fires from GitHub (opened or synchronized).
- 2The flow maps the changed paths to a service name and fetches that SLO's burn rate over 1h and 6h windows from Honeycomb.
- 3A logic step compares both windows against the fast-burn multiplier to decide pass or fail.
- 4It posts the burn math and verdict as a GitHub PR comment.
- 5It sets the commit status check to success or failure to enforce the gate.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HoneycombDistributed traces and queries.
- 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.