DEVOPS
Weekly investigation of repeat build-budget offenders with GitHub issue
Once a week an agent reviews which branches and authors repeatedly overran their build-minute budgets, diagnoses the likely cause from commit and deploy patterns.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly scheduled investigation run
- ActionQuery week's throttle and overage eventsPostgres
- ActionPull commit and deploy metadata for offendersGitHub
- LogicDiagnose root cause and draft remediation
- ActionFile assigned GitHub issue with fix proposalGitHub
- OutputPost weekly offender summary to SlackSlack
What it does
Turns a week of throttle and overage events into an actual action item. An agent reads the throttle history, identifies the branch or author that keeps overrunning, reasons about why from the deploy and commit pattern, and opens a GitHub issue with a recommended fix.
When to use it
Use it when the same branches show up in your throttle alerts week after week and nobody owns fixing the root cause. This converts recurring noise into a triaged, assigned investigation rather than another ignored alert.
How it works
- 1A weekly scheduled trigger kicks off the review.
- 2The agent queries the throttle and overage event history from Postgres for the past week.
- 3It pulls recent commit and deployment metadata from GitHub for the top offending branches to understand the pattern.
- 4The agent reasons about the likely cause, such as a redeploy-on-every-commit loop or oversized build steps, and drafts concrete remediation steps.
- 5It opens a GitHub issue on the relevant repo with the findings and proposed fix, assigned to the branch owner.
- 6It posts a summary of the week's offenders and the filed issue to Slack.
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 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 DevOps workflows
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-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
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.