DEVOPS
Permanent Flag to Config Promoter
Detects flags that have been toggled on permanently and behave like settings rather than experiments.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly audit schedule fires
- ActionQuery always-on single-variant flagsPostgres
- LogicExclude operational kill-switches
- ActionOpen PR promoting flag to configGitHub
- ActionRecord decision in NotionNotion
- OutputNotify platform team in SlackSlack
What it does
Finds long-lived flags that are effectively permanent configuration (always on, never varied, owned by no active experiment) and promotes them out of the flag system into a typed config file, opening a PR for the migration and recording the decision.
When to use it
Use it when your flag store has filled with flags that are really just on/off settings, inflating flag counts and SDK payloads with toggles no one will ever flip back.
How it works
- 1A monthly schedule kicks off the audit.
- 2It queries Postgres for flags that are always-on, single-variant, and older than the permanence threshold.
- 3A filter excludes flags marked as operational kill-switches.
- 4For each candidate it opens a GitHub PR moving the value into a typed config module and removing the flag lookup.
- 5It writes a record to a Notion database documenting the promoted flag and its history.
- 6It notifies the platform team in Slack with the PR and record links.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect NotionPages, databases, comments.
- 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.