DEVOPS
Publish a weekly stale-flag debt digest to Confluence and Slack
Compiles every flag at 100% for 30+ days into a ranked debt report — count, age, and owning team — publishes it to Confluence and posts a summary to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the digest run
- ActionPull flag state and ages from DatadogDatadog
- LogicFilter to 100%-for-30-days and group by team
- ActionEnrich owning team from GitHub historyGitHub
- ActionPublish ranked debt report to ConfluenceConfluence
- OutputPost digest summary to SlackSlack
What it does
This workflow makes flag debt visible without touching any code. Weekly it gathers every flag that has been at 100% for 30+ days, ranks them by age, groups them by owning team, and publishes a clean report to Confluence plus a short summary to Slack. Over time the page shows whether debt is shrinking or growing.
When to use it
Use it when the problem is awareness, not tooling — when leadership wants a trend line on stale flags and teams need a shared scoreboard before you automate removals. It pairs well with the PR-authoring reapers as the reporting layer.
How it works
A weekly schedule fires the run. The workflow pulls flag rollout state and last-change dates from Datadog and filters to flags at 100% for 30+ days. It enriches each with an owning team inferred from GitHub history, then aggregates counts and oldest-flag age per team. It writes or updates a dated Confluence page with the ranked table and a week-over-week delta, and posts a Slack digest linking the page and calling out the worst offenders.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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.