DEVOPS
Block GitLab MR on axe-core accessibility violations in Vercel preview
Crawls the key routes of a Vercel preview deploy with axe-core, fails the GitLab merge request if any serious or critical accessibility violations appear.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionRun axe-core across configured routesShell
- LogicFilter to serious/critical violations
- ActionFail GitLab MR pipeline if any foundGitLab
- OutputComment violations with rule and selectorGitLab
What it does
Runs a dedicated accessibility audit (not just Lighthouse's summary score) across multiple routes of the preview. It enforces a zero-tolerance rule for serious and critical axe violations and reports each violation with its WCAG rule id and the failing element selector.
When to use it
Use it when accessibility compliance is a contractual or legal requirement and a single Lighthouse a11y number is too coarse. Best for teams that need per-element evidence of what broke and where.
How it works
- 1A Vercel deployment-ready webhook supplies the preview URL and MR reference.
- 2A shell step runs axe-core against a configured list of routes and aggregates the JSON results.
- 3A logic branch filters violations down to serious and critical impact levels and counts them.
- 4If the count is above zero, the GitLab MR pipeline is marked failed to block merge.
- 5A comment lists each violation by rule, impact, route, and DOM selector on the MR.
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.