Library · Go
cutline
Release-branch promotion report: which PRs are in one branch but not another
Why it exists
Teams that ship through a branch per environment ask the same questions at every release: what is in stage that prod lacks, what do I pick and in which order, will it conflict, did it all land, and did a hotfix on prod ever come back? Git answers with SHAs, which stop meaning anything after a squash or a cherry-pick, and the tools that do answer are hosted products (Aviator Releases, Runway), a Ruby gem that goes one way (git-pr-release), or conventions of one project (nodejs/branch-diff, electron/unreleased). The comparison with sources is in docs/FAQ.md.
What it does
- 01
search. add fuzzy matching (#101) by Dev
- 02
billing. drop the v1 invoice format (breaking) (#103) by Dev
Next
Smart Rule-Based Approval Engine