DEVOPS
Pre-merge check that flags risky cache-key changes on GitLab MRs
On every GitLab merge request, detects edits to cache keys, lockfiles, or base images that would invalidate the build cache, estimates the rebuild cost from historical data.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab merge request opened or updatedGitLab
- ActionFetch diff and detect cache-key changesGitLab
- LogicRisky cache-invalidating change present?
- ActionEstimate rebuild penalty from historyPostgres
- OutputComment warning on the merge requestGitLab
What it does
When a merge request opens or updates, this flow scans the diff for changes that invalidate the build cache: altered `cache:key` values, new lockfile hashes, or a bumped Docker base image. It looks up how long uncached builds historically took, estimates the added minutes, and leaves an inline warning comment on the MR so the author sees the cost before merging.
When to use it
Use it to shift cache regressions left. Most cache breaks ship by accident in routine dependency bumps; a clear pre-merge heads-up lets the author confirm the change is intentional or scope the cache key more tightly.
How it works
- 1A GitLab merge-request webhook fires on open or update.
- 2The flow fetches the MR diff and detects cache-invalidating edits.
- 3A branch decides whether any risky change is present.
- 4If so, it queries Postgres for historical cached-vs-uncached build durations to estimate the penalty.
- 5It posts a warning comment on the MR naming the change and the expected slowdown.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.