ENGINEERING
Mirror Sentry release health into a GitHub commit status for the deploy
On a Sentry release regression, sets a failing GitHub commit status on the release SHA and posts the crash-free comparison as a PR comment so the merge that triggered the Vercel…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry release regression event with commitSentry
- ActionFetch new vs baseline crash-free rateSentry
- LogicCompare delta and decide pass or fail
- ActionSet commit status on release SHAGitHub
- OutputPost crash-free comparison as PR commentGitHub
What it does
Brings release-health verdicts back to where the code lives. When Sentry detects a crash-free regression on a new release, this workflow resolves the commit SHA behind it and writes a GitHub commit status plus a PR comment with the baseline-versus-new comparison. Engineers see the failing health gate next to the change that caused it, not buried in a dashboard.
When to use it
Use it when your promotion gate should live in GitHub checks rather than a separate channel, so a regressed release blocks visibly on the originating pull request. Pairs well with branch protection that watches the release-health status.
How it works
- 1Sentry emits a release regression event carrying the release version and commit.
- 2The flow fetches the new release's crash-free rate and the baseline from Sentry.
- 3A logic step compares the delta to your threshold and decides pass or fail.
- 4It sets a success or failure commit status on the release SHA in GitHub.
- 5On failure it posts a PR comment with the crash-free numbers so reviewers can hold the Vercel promotion.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.