ENGINEERING
Auto-unfreeze GitHub deploys when the SLO budget recovers
On a schedule, this flow re-checks the Honeycomb SLO and, once the burn rate has cooled below the safe threshold for a sustained window, lifts the GitHub deploy freeze and tells…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: re-check SLO every few minutes
- ActionQuery Honeycomb SLO burn rate + budgetHoneycomb
- LogicConfirm sustained recovery + active freeze
- ActionDisable GitHub deploy-freeze rulesetGitHub
- OutputPost 'deploys reopened' to SlackSlack
What it does
Closes the loop on a deploy freeze. It periodically queries the Honeycomb SLO that triggered a freeze and, when burn rate has stayed under the safe threshold long enough to trust the recovery, disables the lockdown branch ruleset in GitHub and announces that deploys are open again.
When to use it
Pair it with a burn-rate freeze job so freezes lift themselves instead of lingering until someone remembers. Use it for any service where a recovered error budget should restore normal shipping without manual toggling.
How it works
- 1A schedule fires every few minutes during business hours.
- 2The flow queries the Honeycomb SLO for current burn rate and budget remaining.
- 3A logic step confirms burn rate has stayed below the safe threshold for the full sustained window and that a freeze is actually active.
- 4If clear, GitHub disables the deploy-freeze ruleset to restore normal merges.
- 5A Slack message announces deploys are reopened, with the recovered budget figure.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
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.
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.
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.
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…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.