25 stale branches archived by rename, and the repository audit passes
Satsuma's code is spread across a set of GitHub repositories, and an audit checks them for unmerged branches that have gone stale. 25 such branches were renamed to sit under an archive prefix, with every commit kept, so the audit skips them. After the rename the audit passed cleanly for all 14 active repositories.
The choice was to keep the stale work rather than delete it. Renaming moves it out of the audit's way while leaving the history readable for anyone who needs it later.
One side effect stays open: "Renaming on GitHub doesn't update your local checkouts." Local copies of the affected repositories, satsuma-website among them, still track the old branch names and each needs to be pruned and pointed at the archived name.
The audit does not yet run on its own each week; it is waiting on a credential. Other organisation housekeeping is still open: renaming the default branch of satsuma-book, setting the organisation's email and X handle, and verifying the satsuma.one domain.
- Keep the stale branches but rename them under an archive prefix instead of deleting them
- Local checkouts still track old branch names; each affected repository needs pruning and its branch pointed at the archived name
- The weekly audit is not yet running; it needs a credential
- Rename satsuma-book's default branch
- Set the organisation's email and X handle, and verify the satsuma.one domain