ENGINEERING
Pre-flight source-map check on GitLab merge requests
When a GitLab MR pipeline completes, it dry-run uploads the built source maps to a Sentry staging release and verifies symbolication before the MR can merge.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR pipeline success eventGitLab
- ActionUpload MR build maps to staging Sentry releaseSentry
- LogicProbe symbolication and compare to expected paths
- ActionSet passing or failing commit status on MRGitLab
- OutputPost MR note with verification summaryGitLab
What it does
It catches broken source-map configuration before code ever reaches production. On each GitLab merge request pipeline, it pushes the MR's built artifacts to a throwaway Sentry release, validates that frames symbolicate, then writes the result back as an MR note and commit status so reviewers see green or red.
When to use it
Use it when source-map regressions (wrong `sourceMappingURL`, missing `release`, stripped maps) only surface after merge. This shifts the check left so the author fixes it in the MR, not in a postmortem.
How it works
- 1A GitLab pipeline-success event fires for an open merge request.
- 2The flow uploads the MR build's source maps to a temporary Sentry release named for the MR.
- 3A logic step runs a symbolication probe and compares resolved frames against expected source paths.
- 4On success it sets a passing commit status; on failure it sets a failing status.
- 5It posts an MR note summarizing artifact count, resolved frames, and any errors, then deletes the staging release.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SentryErrors, performance, releases.
- 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.