From ff854f2a7237b308f59fb888e60dee69812663da Mon Sep 17 00:00:00 2001 From: junior Date: Sun, 5 Jul 2026 13:35:50 +0000 Subject: [PATCH 1/2] docs: clarify per-agent authentication via TOKEN_* secrets (#60) --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index d361f23..0d3ef04 100644 --- a/README.md +++ b/README.md @@ -79,7 +79,8 @@ points `$SCRIPTS` at it. Keep the workflow and its scripts moving together on `m | `AGENT_TOKEN` | PAT (issue/repository/organization/misc read+write, cross-repo) — posts the delegation comment that fires the next agent **and** powers the `gitea-api` skill (read/write issues, PRs, comments, labels, and Actions runs/logs across any repo). Do not re-narrow its scopes without also removing the `gitea-api` skill. | | `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. Tip: set these once at the **org** level so every repo inherits +`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 them via `secrets: inherit`. ## Also add to each consuming repo -- 2.54.0 From 455306062759ab9f5b63918d5390a981f6c4942c Mon Sep 17 00:00:00 2001 From: junior Date: Sun, 5 Jul 2026 13:35:58 +0000 Subject: [PATCH 2/2] docs(README): clarify how per-agent tokens control Gitea authentication --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 0d3ef04..ccd7f24 100644 --- a/README.md +++ b/README.md @@ -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 -- 2.54.0