Gitea API token needs read:issue + write:issue scope for agent workflows #15
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
The Gitea credential available to agent sessions could push code but not read/create issues (
required=[read:issue], token scope=write:repository), which is why B1–B5 were originally written todocs/BACKLOG-2026-07-16.mdinstead of Gitea issues directly.Fix: create a token at git.jerodrigged.com/user/settings/applications with
read:user,write:issue,write:repositoryand set it asGITEA_TOKEN(user env var).Status: appears already resolved — this issue itself was created via the API using the current
GITEA_TOKEN, which succeeded, confirming the token now has the needed scopes. Closing on creation; reopen if issue-write ever regresses.Migrated from
docs/BACKLOG-2026-07-16.md.