A fix lands
GitHub sends a Pull request event when a labelled change is merged.
A gentle guardrail for releases
The merge is
The merge is
not the end.
BackportGuard notices the fixes that should travel further, then opens one clear reminder for the branches that still need them.
release topologywatching
01One reminder
A single issue keeps the target branches visible without automating a risky change.
Signed
GitHub's SHA-256 signature is checked before anything is processed.
Idempotent
SQLite remembers delivery IDs, so retries do not multiply work.
Small
FastAPI, SQLite and a narrow webhook surface. Nothing more.
The signal travels.
You keep control.
BackportGuard does the boring, important part: it remembers. Your team still decides whether and how to apply the fix.
Branches are known
The service reads the repository's small, declarative .backportguard.yml file.
An issue is opened
The release owners get a concise checklist of branches to review. No code is copied.
One file. A quieter release day.
Put the backport policy beside the code it protects. The service does the rest.
branches:
- release/1.2
- release/1.1
labels:
required:
- backport
Start with the policy.
Add this file to a repository, install the GitHub App, then point its Pull request webhook at BackportGuard.
Read the installation guide ↗