DEVOPS
Score PR Deploy Risk From Diff Size and Touched Paths
When a pull request opens or updates, it scores release risk from the diff (lines changed, files touched.
How it runs
The automated pipeline, trigger to output.
- TriggerPR opened or updated (GitHub webhook)GitHub
- ActionFetch PR diff and changed filesGitHub
- LogicCompute weighted risk score from diff
- LogicMap score to Low / Medium / High
- OutputApply risk label and post verdict commentGitHub
What it does
This workflow inspects every pull request the moment it opens or gets new commits, computes a deploy-risk score from the diff, and writes a clear Low/Medium/High verdict directly onto the PR as a label and comment so reviewers see risk before they approve.
When to use it
Use it when your team merges fast and you want a consistent, automatic signal for which PRs deserve a closer review or a staged rollout — without relying on each author to self-assess.
How it works
- 1A GitHub pull_request webhook fires on opened or synchronize events.
- 2The flow fetches the PR diff and file list from the GitHub API.
- 3A scoring step weights additions, deletions, file count, and high-blast-radius paths (db migrations, auth, payment, infra config) into a 0-100 risk score.
- 4A branch maps the score into Low, Medium, or High tiers.
- 5The flow applies the matching risk label and posts a comment summarizing what drove the score back onto the PR.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.