gitea/agents
8
0
Fork 0
Code Issues 2 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs(README): clarify how per-agent tokens control Gitea authentication

Browse Source
This commit is contained in:
junior
2026-07-05 13:36:07 +00:00
parent ff854f2a72
commit 4553060627
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -1
View File
@@ -80,7 +80,8 @@ points `$SCRIPTS` at it. Keep the workflow and its scripts moving together on `m
| `TOKEN_PM`,`TOKEN_SENIOR`,`TOKEN_JUNIOR`,`TOKEN_LEAD`,`TOKEN_QA` | optional — post/commit as each agent's own Gitea user (falls back to the bot) |
`GITEA_TOKEN` is auto-provided, while per-agent `TOKEN_*` secrets let each agent authenticate and
post as its own Gitea user. Tip: set these once at the **org** level so every repo inherits
post as its own Gitea user; otherwise the shared `AGENT_TOKEN` bot account is used.
Tip: set these once at the **org** level so every repo inherits
them via `secrets: inherit`.
## Also add to each consuming repo