DEVOPS
Block GitLab MR merge on bundle budget breach
On preview deploy, fails a GitLab commit status when the bundle delta exceeds the configured budget threshold, blocking merge until the regression is resolved.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment succeededVercel
- ActionSum client bundle bytesVercel
- ActionRead baseline and compute deltaBigQuery
- LogicBranch on budget threshold breach
- OutputSet pass/fail GitLab commit statusGitLab
What it does
This workflow turns bundle budgets into a hard merge gate. After a Vercel preview build, it compares the new bundle size against the target-branch baseline in BigQuery. If the increase exceeds the configured threshold (absolute KB or percent), it sets a failed GitLab commit status on the MR head; if within budget, it sets a passing status. With the status marked required in GitLab, an over-budget MR cannot merge.
When to use it
Use it when warning comments are not enough and you need budget enforcement that actually stops a regression from shipping. Best paired with the baseline-recording workflow.
How it works
- 1Vercel `deployment.succeeded` webhook fires for a preview build.
- 2Sum the build's client bundle bytes via the Vercel API.
- 3Read the target-branch baseline from BigQuery and compute the delta.
- 4Branch: if delta exceeds the budget threshold, fail; otherwise pass.
- 5Set the corresponding pass/fail GitLab commit status on the MR head SHA.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BigQueryDatasets, queries, schemas.
- 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
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.