DEVOPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR opened or updatedGitHub
- LogicDetect changed Space hardware tier in diff
- ActionLook up tier hourly rate from HF catalogHugging Face
- LogicCompare projected monthly cost to ceiling
- OutputPost approve or warning PR commentGitHub
What it does
Reviews pull requests that touch a Hugging Face Space's hardware setting (README metadata or config). It looks up the requested tier's price, projects the always-on monthly cost, and leaves a GitHub comment approving cheap changes or warning when an upgrade would blow past the budget ceiling.
When to use it
When Spaces are configured as code and a reviewer might miss that someone bumped a demo from free CPU to an A10G GPU. Catch the cost at review time, not on the invoice.
How it works
- 1A GitHub pull_request webhook fires when a PR opens or updates.
- 2Read the changed files and detect a modified Space hardware tier.
- 3Map the new tier to its hourly rate via the Hugging Face hardware catalog and project monthly cost.
- 4A branch checks the projected cost against the configured ceiling.
- 5Post a GitHub PR review comment: a green note under budget, or a flagged warning with the dollar delta and who to ping for sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.
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.
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.
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.