ENGINEERING
Sentry resolve verification linking the fixing commit back to GitLab
When a Sentry issue is marked resolved, it verifies a fixing deploy actually shipped, confirms which commit resolved it via GitLab.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue marked resolvedSentry
- ActionCheck recent GitLab deploys for matching commitGitLab
- LogicBranch on whether a fixing deploy exists
- ActionIdentify fixing commit and author via blameGitLab
- OutputClose linked GitLab issue with attribution noteGitLab
What it does
Closes the loop after a fix. When someone resolves a Sentry issue, this flow confirms a deploy containing a relevant commit actually went out, identifies that fixing commit in GitLab, and then closes the originally linked GitLab issue with a note attributing the resolution to the specific commit and author. It guards against premature resolves that have no shipped fix behind them.
When to use it
Use it to keep Sentry and GitLab in sync and to maintain an accurate record of which commit fixed which error. Good for teams that want resolution hygiene and an auditable trail tying every closed error to a real change.
How it works
- 1Sentry fires when an issue is marked resolved.
- 2The flow checks recent GitLab deploys for a commit touching the issue's offending file.
- 3If no matching deploy is found, it reopens the Sentry issue and flags it as unverified.
- 4If found, it identifies the fixing commit and author via blame on the changed lines.
- 5It closes the linked GitLab issue with a resolution note crediting that commit.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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.