DEVOPS
Escalate imminent base-image EOL to PagerDuty
Checks each tracked base image against its EOL date and, when a production image crosses into the final countdown window with no open rebuild PR, raises a PagerDuty incident…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule runs the deadline check
- ActionLook up EOL dates for tracked production imagesHTTP webhook
- LogicKeep only images inside the imminent window
- ActionCheck GitHub for an open rebuild PR or issueGitHub
- LogicKeep imminent images with no remediation in flight
- OutputRaise a PagerDuty incident and post a Slack summaryPagerDuty
What it does
This is the last line of defense. It watches base images whose end-of-life date is now imminent, confirms there is no rebuild already in flight, and escalates the unaddressed ones as a PagerDuty incident so an owner is paged before support actually ends.
When to use it
Use this for the small set of business-critical images where a missed EOL is unacceptable. It complements the daily scan by guaranteeing that a near-deadline image with no remediation underway becomes an actionable incident, not a Slack message someone scrolled past.
How it works
- 1A daily schedule runs the deadline check.
- 2The workflow pulls tracked production images and looks up each EOL date over HTTP.
- 3A logic step keeps only images inside the imminent window (e.g. 7 days).
- 4For each it checks GitHub for an open rebuild PR or issue.
- 5A second logic branch keeps only imminent images with no remediation in flight.
- 6It opens a PagerDuty incident per unaddressed image and posts the escalation summary to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.