Branch sweep on origin found 12 stale remote branches that have no open PR and look safe to delete.
Merged but not deleted (3)
Closed-rejected (6)
PR-less orphans (3)
- `chore/rebase-ht-2026-05-16` — looks like a stale rebase attempt
- `ci/server/fix-slow-test` — looks abandoned
- `feat/chain-picker` — looks abandoned
Asking permission
These deletions are visible external actions, so I'm filing rather than acting. Two options:
A. Bulk-delete all 12. Quick, clears the namespace. The closed/rejected PRs retain their branch SHAs in GitHub's PR-archive so references aren't lost; the merged ones are reachable via the merge commits.
B. Delete only the merged-undeleted (3) and PR-less (3); keep closed-rejected (6). Conservative. Keeps the 6 rejected-feature branches around as "this is what was tried" archaeology.
I'd lean B as the default since closed-but-not-merged branches occasionally get reopened or referenced; merged + orphan are unambiguously safe.
(Won't block on this — just leave a reply when convenient. Filed to track since the sweep already had to surface them.)
Branch sweep on origin found 12 stale remote branches that have no open PR and look safe to delete.
Merged but not deleted (3)
Closed-rejected (6)
PR-less orphans (3)
Asking permission
These deletions are visible external actions, so I'm filing rather than acting. Two options:
A. Bulk-delete all 12. Quick, clears the namespace. The closed/rejected PRs retain their branch SHAs in GitHub's PR-archive so references aren't lost; the merged ones are reachable via the merge commits.
B. Delete only the merged-undeleted (3) and PR-less (3); keep closed-rejected (6). Conservative. Keeps the 6 rejected-feature branches around as "this is what was tried" archaeology.
I'd lean B as the default since closed-but-not-merged branches occasionally get reopened or referenced; merged + orphan are unambiguously safe.
(Won't block on this — just leave a reply when convenient. Filed to track since the sweep already had to surface them.)