Strip Forgejo theme inheritance — 0.5.1 #10
No reviewers
Labels
No labels
agent-work
agent-working
ultracode
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-platform/app-template!10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "strip/theme-inherit"
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?
Live testing surfaced a Forgejo OAuth reality: tokens are re-issued from the ORIGINAL grant, so the added
read:userscope never reaches existing users' tokens without a manual revoke under Settings → Applications (fresh sign-in proven to 403/user/settings). A feature needing a hidden consent dance is quiet brokenness — stripped. The brand-green tokens stay. 35/35 tests.Stripped after live testing: Forgejo re-issues OAuth tokens from the ORIGINAL grant, so a scope added later never reaches the token unless the user first revokes the app under Settings → Applications — proven with a fresh sign-in whose token 403s /user/settings ("does not have required scope read:user"). A feature that needs a hidden consent dance to work is quiet brokenness; out it goes. The brand-green tokens (0.5.0's other half) stay. version 0.5.1.