DEVOPS
Post Lighthouse budget result as a GitHub PR status check
On each Vercel preview deploy tied to a pull request, runs Lighthouse and writes a required GitHub commit status that turns the merge button red until the performance budget…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment ready for PRVercel
- ActionRun Lighthouse audit on preview URLBrowserbase
- LogicEvaluate scores against budget
- OutputWrite GitHub commit status check on the SHAGitHub
What it does
This turns your Lighthouse budget into a hard branch-protection gate. When a preview deploys for a PR, the workflow audits it and writes a GitHub commit status check; a failing budget marks the check red so the PR cannot be merged until performance is fixed, and a passing budget unblocks it.
When to use it
Use this when you want the QA gate enforced in GitHub itself rather than as a Slack notification. Pair it with a required status check in branch protection so a slow page literally cannot reach main.
How it works
- 1A Vercel deployment-ready webhook fires for a preview tied to a PR branch and commit SHA.
- 2A Lighthouse run audits the preview URL and captures category scores plus key metrics like LCP and TBT.
- 3A logic step decides pass or fail against your budget.
- 4The workflow posts a GitHub commit status (success or failure) on the exact SHA, with a target link to the report.
- 5The PR's required check reflects the result, gating the merge button automatically.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.