Fourteen housekeeping changes merged and the satsuma-mini repository deleted
Satsuma's code lives in private repositories on GitHub, grouped under one organisation. In the lab's work on that organisation, all 14 open pull requests from a round of housekeeping were squash-merged, and their branches were deleted.
The satsuma-mini repository was permanently deleted from GitHub. The deletion was deliberate: the repository is not to be pushed or recreated. It was private and up for only a few hours. The repository and its preview image were also removed from the members' page kept in .github-private. The local copy keeps its full history, with its GitHub remote removed, and nothing of satsuma-mini was pushed anywhere.
A second session was doing cleanup work across the other repositories at the same time. It was told to drop the satsuma-mini item, discard its copy and carry on with the rest. That message was queued and has not been confirmed as read, and a reply to a question from that session is queued until its current turn finishes.
Still open: whether the 25 unmerged stale branches should be moved under an archive prefix or deleted.
- Squash-merging all 14 housekeeping pull requests and deleting their branches
- Permanently deleting the satsuma-mini repository and removing it from the members' page
- Telling the parallel cleanup session to skip and discard satsuma-mini
- satsuma-mini was deleted on purpose and must not be pushed or recreated
- The cleanup session drops the satsuma-mini item, discards its copy and continues with the other repositories
- Whether the 25 unmerged stale branches should be moved under an archive prefix or deleted