DEVOPS
Lead-Time-for-Changes from PR Merge to Production
When a production deployment finishes, traces every commit back to its merged pull request, computes lead time for changes per PR.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub production deployment-status webhook (success)GitHub
- ActionList commits between previous and current production SHAGitHub
- ActionResolve merged PR and merge timestamp per commitGitHub
- LogicCompute per-PR lead time, drop PR-less direct pushes
- OutputBatch-insert lead-time rows into SnowflakeSnowflake
What it does
This workflow measures lead time for changes: the elapsed time from a pull request being merged to the code reaching production. On each successful production deploy it resolves the commits shipped, looks up the merge timestamp of each commit's PR, calculates per-PR lead time, and inserts the rows into a Snowflake table that powers your DORA dashboard.
When to use it
Use it when you need accurate, commit-level lead-time data instead of rough averages, and you already warehouse engineering metrics in Snowflake for BI tooling. Good for teams that report DORA quartiles to leadership.
How it works
- 1A GitHub deployment-status webhook fires when a production deploy reaches `success`.
- 2The flow compares the deploy SHA to the previous production SHA and lists every commit in between.
- 3For each commit it queries GitHub for the associated merged PR and its merge timestamp.
- 4A logic step computes lead time as deploy time minus PR merge time, skipping direct pushes that have no PR.
- 5The final step batch-inserts one row per PR (repo, PR number, merged-at, deployed-at, lead-time seconds) into Snowflake.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 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
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.