DEVOPS
Block GitLab MR promotion until Vercel preview passes Lighthouse
When a Vercel preview deploy finishes for a GitLab merge request, run Lighthouse against the preview URL and block promotion to staging unless performance, accessibility.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionRun Lighthouse CLI against preview URLShell
- LogicCheck each category against threshold
- ActionSet GitLab pipeline status (fail blocks merge)GitLab
- OutputComment score breakdown on the MRGitLab
What it does
Gates merge-request promotion on real Lighthouse results from the live Vercel preview. The MR cannot advance until the deploy hits every category threshold, and the four scores are posted as an MR comment so reviewers see exactly where it stands.
When to use it
Use it when your team merges to staging through GitLab and you want a hard quality floor instead of a courtesy reminder. Ideal for product teams that have been shipping regressions in performance or accessibility that slipped past human review.
How it works
- 1A Vercel deployment-ready webhook fires with the preview URL and the source MR.
- 2A shell step runs the Lighthouse CLI against the preview URL and emits JSON for all four categories.
- 3A logic branch compares each category score against its configured threshold.
- 4If any category fails, the GitLab pipeline status is set to failed, blocking the merge.
- 5Either way, a comment with the per-category scores and pass/fail verdict is posted to the MR thread.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 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
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.
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.
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.
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…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-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.