ccyh7789/merged-branch-evidencev0.1.0Public
Merged branch evidence
Decides which local branches are safe to delete, and says why for each one.
Read the full description
`git branch --merged` answers a narrower question than the one you are asking: it reports whether the base branch contains the branch tip as an ancestor, which is true after a merge commit or a fast-forward and false after every squash and every rebase. On a repository that squashes, branches whose work shipped weeks ago keep reporting as unmerged, and `git cherry` agrees with it because a squash rewrites the patch ids too. This play gathers four independent sources instead: reachability, the pull request number GitHub appends to a squash commit subject, the pull request state from gh, and whether the branch still holds commits the base does not. It then names a verdict per branch with the evidence behind it. Two failure directions matter and both appear here: a branch that merged invisibly and gets kept forever, and a branch whose pull request merged but which has kept receiving commits since, where deleting on the strength of `merge
Before you run it3 local tools
Everything here is checked on your machine when rote inspects the play. This page never learns what you have installed or which credentials you hold.
- ○gitlocal tool
Must be on your PATH when used. minimum version undeclared.
- ○python3local tool
Must be on your PATH when used. minimum version undeclared.
- ○ghlocal tooloptional
Must be on your PATH when used. minimum version undeclared.
Inputs3, 1 required
rote asks for these before running and shows the defaults it will use.
- Repo
repoPath to the git repository to inspect. Steps run in the play workspace rather than your shell, so pass the path you mean rather than a relative one.
requiredstringexample/Users/me/src/my-projectcustom value allowed - Base
baseThe branch work lands on, without the origin/ prefix.
optionalstringdefaultmainexampledevelopcustom value allowed - Scan commits
scan_commitsHow far back on the base branch to look for squash commit subjects. A branch whose squash is older than this window falls back to the pull request lookup.
optionalintegerdefault600example2000custom value allowed
What it changes
No write operations are declared in this version's manifest.
Credentials remain in the recipient's local rote vault; this page and the publisher never receive them.
Runtime details
- rote CLIversion 0.62.0 or newer
- Servicesnone declared
- Digest
sha256:cd0619ec9c58bbeea267cf59d6c7cc8c81404b47b2e455da4d7f458d417b73cc - Archive size29556 bytes
- Published2026-09-02T15:22:50.849962+00:00
- Published withrote 0.78.0
Credential values and current readiness remain local. Opening this page never prompts for a credential, opens an authorization browser, or calls a service this play uses.
A play is a published, versioned automation package that runs on your own machine through rote, a free command-line tool. Opening this page installs nothing and runs nothing.