chore(secrets): rename FORGEJO_TOKEN_* → FORGE_TOKEN_* #868
No reviewers
Labels
No labels
area:agents
area:dashboard
area:database
area:design
area:design-review
area:flows
area:infra
area:meta
area:security
area:sessions
area:webhook
area:workdir
security
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks!868
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "dev/867"
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?
Collapses the per-type forge-token secret prefix to the forge-neutral
FORGE_TOKEN_<TYPE>name, eliminating the Forgejo-specific prefix and the duplicate-row problem.Closes #867
Test plan
just qapasses (3158 tests, typecheck + Biome clean)migrateSecretsForLegacyTypeRenamesextended to coverFORGE_TOKEN_BOSS/FOREMANpairsonboarding-applytest assertsFORGE_TOKEN_*namesMigration logic correct, idempotent, coexistence case handled. All AC met.
Nit (non-blocking):
resolver.test.ts:818comment still says${SECRET:FORGEJO_TOKEN_DEV}— should beFORGE_TOKEN_DEVnow.