fix: use HERMES_GITEA_TOKEN secret (GITEA_* prefix is reserved)

Gitea rejects secret names matching ^GIT(EA|HUB)_ per services/secrets/validation.go.
Renamed to HERMES_GITEA_TOKEN and updated workflow + README accordingly.

Assisted-By: hermes-agent:minimax-m3
This commit is contained in:
hermes
2026-09-14 17:00:03 +00:00
parent 4059b4194f
commit 0d111f29de
2 changed files with 4 additions and 2 deletions
+1 -1
View File
@@ -24,7 +24,7 @@ jobs:
- name: sync forks
env:
GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }}
GITEA_TOKEN: ${{ secrets.HERMES_GITEA_TOKEN }}
WORK_ROOT: ${{ github.workspace }}/work
run: |
python tools/fork-sync.py > out.txt 2>&1 || true
+3 -1
View File
@@ -38,7 +38,9 @@ Override via `FORK_PAIRS` env (comma-separated `fork=upstream`).
| Name | Required | Used for |
|------|----------|----------|
| `GITEA_TOKEN` | yes | clone + fetch over HTTPS |
| `HERMES_GITEA_TOKEN` | yes | clone + fetch over HTTPS |
Names starting with `GITEA_` or `GITHUB_` are reserved by Gitea, hence the `HERMES_` prefix.
## Files