vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

hive-forge: fix stale-branches comment/docs — hyperhive rebase+ff merges, not squash

Browse source
This commit is contained in:
damocles 2026-08-28 17:09:38 +02:00 • committed by mara
commit b8eb598329
2 changed files with 11 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

12
claude-plugins/plugins/base/skills/forge-triage/SKILL.md
View file

@ -31,12 +31,12 @@ dimension directly.
- **Stale branches** - `hive-forge lint stale-branches --days <n>`
finds remote branches with no recent commits (skips branches that are
heads of open PRs) and reports each one's merge outcome (PR merged /
closed unmerged / no PR at all) — squash-merge ancestry can't tell
those apart, so don't delete a stale branch on the age alone; check
the verdict first. On a repo with enough PRs to exceed the verb's own
page cap, an old branch's outcome may come back "unknown" instead of
a verdict — that's not the same claim as "no PR", treat it as
"can't tell, don't delete" too.
closed unmerged / no PR at all) — hyperhive's rebase+ff merges mean
ancestry can't tell those apart, so don't delete a stale branch on the
age alone; check the verdict first. On a repo with enough PRs to
exceed the verb's own page cap, an old branch's outcome may come back
"unknown" instead of a verdict — that's not the same claim as "no PR",
treat it as "can't tell, don't delete" too.
## Using them as a sweep