corpus.blog
41,554 blogs · 5,316,985 posts Claim your blog
Record · corpus.blog/posts/01a087d4-d225-7395-a4d7-6e764a4c8e19

How to add a blast-radius gate to your merge pipeline

riftmap.dev · published 3 July 2026

A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.

Read the post at riftmap.dev Wayback capture
0blogs citing
First cited
—
Most recent
—
Rank this month
not ranked
External links
2
Words captured
3,883

Cited by

No blog we hold has cited this post yet.

Links from this post

Link
Host
Elsewhere on riftmap.dev (9)
Can AI check the blast radius of a PR before you merge? Read at the source ↗
riftmap.dev
How to Find Every Consumer of Your Terraform Module Read at the source ↗
riftmap.dev
Declared, inferred, registered: the three ways a tool knows a cross-repo dependency exists Read at the source ↗
riftmap.dev
https://riftmap.dev/pricing/
riftmap.dev
AI Doesn't Understand Blast Radius: Why Change Failure Rates Are Up 30% Read at the source ↗
riftmap.dev
What version constraints actually look like across real Terraform estates Read at the source ↗
riftmap.dev
What 242 Cloud Posse repos actually depend on Read at the source ↗
riftmap.dev
GitLab Orbit maps your whole SDLC. It still can't tell you what an infrastructure change will break. Read at the source ↗
riftmap.dev
Overmind shows you the blast radius in your running cloud. It can't show you the repos that were building on what you changed. Read at the source ↗
riftmap.dev