Development record
The reservations ruleset forbids deleting refs/heads/abcd-reserved/** with no bypass, so every spent reservation branch stays on the forge forever, counting against its per-repository branch limits and against the intent's 'needs occasional clean-up' (decision 10 of itd-2609091034175565); the rulesets README notes the itd-118 sweep needs the ruleset amended first.
issueresolvedminoriss-2610142200389875
The reservations ruleset forbids deleting refs/heads/abcd-reserved/** with no bypass, so every spent reservation branch stays on the forge forever, counting against its per-repository branch limits and against the intent's 'needs occasional clean-up' (decision 10 of itd-2609091034175565); the rulesets README notes the itd-118 sweep needs the ruleset amended first.
Frontmatter
| id | iss-2610142200389875 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610142200389875-the-reservations-ruleset-forbids.md
open on GitHub ↗ · commit history ↗
mentions5
- adr-2610161940004937Spent reservation branches are deleted only by one GitHub App the ruleset names
- itd-118Merged work leaves no residue: abcd-managed repos delete a PR branch on merge, and abcd tidies the stale local branch, tracking ref, and worktree
- itd-2609091034175565Before an agent starts on an item, it reserves it on the shared remote, and everyone who works on the project sees the reservation
- itd-2610222214476887One command shows everything a repository has left lying around, and clears what is provably finished
- spc-2610230730269295`abcd sweep`: one dry run over every leftover, and `--apply` for what is provably spent