Gitea API token needs read:issue + write:issue scope for agent workflows #15

Closed
opened 2026-07-19 22:16:12 -06:00 by jhodgkin · 0 comments
Owner

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 to docs/BACKLOG-2026-07-16.md instead of Gitea issues directly.

Fix: create a token at git.jerodrigged.com/user/settings/applications with read:user, write:issue, write:repository and set it as GITEA_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.

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 to `docs/BACKLOG-2026-07-16.md` instead of Gitea issues directly. **Fix:** create a token at git.jerodrigged.com/user/settings/applications with `read:user`, `write:issue`, `write:repository` and set it as `GITEA_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`.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jhodgkin/lisilou-portfolio#15