DEVOPS
Run preview QA checklist when a PR is labeled ready-for-qa
When a reviewer adds the ready-for-qa label, finds the PR's Vercel preview, runs an interactive QA checklist in the browser.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR labeled eventGitHub
- LogicPass only the ready-for-qa label
- ActionResolve latest Vercel preview for the PR branchVercel
- ActionRun checklist items in headless browserBrowserbase
- LogicCompile pass/fail/skipped counts
- OutputPost checklist report and swap labels on PRGitHub
What it does
This workflow puts QA on demand. Adding the `ready-for-qa` label to a pull request triggers a full checklist run against that PR's live Vercel preview: each item is a scripted browser interaction, and the results come back as a tidy markdown report in the PR conversation.
When to use it
Use it when not every commit needs QA but reviewers want a one-click way to validate a candidate before merge, with a documented checklist trail attached to the PR.
How it works
- 1GitHub fires a `pull_request labeled` event; a logic step passes only the `ready-for-qa` label.
- 2The workflow queries the Vercel API for the latest ready preview deployment on that PR's branch.
- 3Browserbase executes each checklist item against the preview, capturing per-step screenshots.
- 4A logic step compiles items into pass, fail, and skipped counts.
- 5A formatted checklist report with screenshots is posted as a PR comment.
- 6If any item failed, the `ready-for-qa` label is removed and `qa-failed` is applied.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect BrowserbaseHeadless browsers, sessions, replays.
- 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.