DEVOPS
Post a Lighthouse scorecard comment on every preview PR
On each new Vercel preview, runs Lighthouse and posts a formatted scorecard as a sticky GitHub PR comment showing each category score and whether it improved or regressed versus…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionRun Lighthouse on preview URLShell
- ActionRead and store baseline scoresPostgres
- LogicCompute per-category deltas
- OutputUpsert sticky scorecard comment on PRGitHub
What it does
This workflow gives reviewers an at-a-glance quality scorecard inside the pull request. For every preview deploy it audits the preview URL with Lighthouse, looks up the stored scores for the PR's base branch, and posts a single sticky comment that lists each category with an up or down delta. The comment updates in place on each new push so the PR always shows current numbers.
When to use it
Use it when you want visibility into performance and accessibility trends per PR without blocking merges — a softer, informational counterpart to a hard gate.
How it works
- 1A Vercel preview-ready webhook supplies the preview URL, PR number, and base branch.
- 2A shell step runs Lighthouse and captures the category scores.
- 3An action reads the baseline scores for the base branch from Postgres, then writes the new scores back for next time.
- 4A logic step computes the per-category deltas and formats a markdown scorecard table.
- 5An action upserts a sticky comment on the GitHub PR with the scorecard, replacing any prior comment from this workflow.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 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
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.