DEVOPS
Record every flag rollout change with its health snapshot to BigQuery
On each flag-config change pushed to GitHub, it captures who changed what plus a Honeycomb health snapshot of the affected cohort and appends an immutable audit row to BigQuery…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub webhook on flag-config change to mainGitHub
- ActionExtract flag change metadata from the diffGitHub
- ActionCapture Honeycomb health snapshot for the serviceHoneycomb
- LogicAssemble normalized audit record
- ActionAppend audit row to BigQueryBigQuery
- OutputPost one-line entry to Slack release logSlack
What it does
Builds a durable audit trail of feature-flag rollouts. Every change is logged with its author, the before/after state, and a point-in-time health snapshot so you can reconstruct exactly what was live when an incident happened.
When to use it
Use when you need rollout history for postmortems, compliance evidence, or to correlate flag changes against later incidents. It is read-only on production and adds no rollback behavior of its own.
How it works
- 1A GitHub webhook fires when a flag-config file is changed on the main branch.
- 2A GitHub action reads the diff to extract the flag name, author, old percentage, and new percentage.
- 3A Honeycomb query captures the current error rate and latency for the affected service.
- 4A logic step assembles a normalized audit record from the change metadata and the health snapshot.
- 5A BigQuery action appends the row to the rollout-audit table.
- 6A Slack confirmation posts a one-line entry to the release log channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HoneycombDistributed traces and queries.
- 3Connect BigQueryDatasets, queries, schemas.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.