rotate-token: a none group is never a Forgejo token #51
No reviewers
Labels
No labels
blocked
bug
decision
duplicate
enhancement
help wanted
invalid
landed?
question
ready-to-merge
stale
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/nexus!51
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/rotate-token-none-selectors"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Three fixes to how
rotate-tokentreats a registry group whoseserviceisnone, found by a cross-family review of allod/nexus#50 after it merged. The--forgejo-tokenselector no longer resolves to anonegroup that still carries placeholder account and token-name fields, so it cannot rotate an unrelated credential. The single-secret warning and the refusal for one member of a multi-secret group now print generic copy for anonegroup instead of naming a Forgejo UI token it does not have or suggesting a--forgejo-token /that cannot exist. Everyforgejogroup behaves exactly as before. What proves it: the suite passes with two new tests covering each path. If it is wrong, revert; the previous behavior was only over-permissive, not broken, forforgejogroups.Refs allod/tools#182. Review: gpt-5.6-sol via pi, thinking high, on the merged diff of allod/nexus#50; three findings, all three reproduced against the source and fixed here.
Risk
R1. Selector narrowing and printed copy; no change to what is encrypted or written.
Validation
bash tests/rotate-token.sh: 39 passed, includingforgejo-token selector ignores a none groupandnone group single-secret copy is generic.