ci: push docs-regen commit with a real account token, not the default bot #176

Merged

rootiest merged 1 commits from ci/bot-push-token into main 2026-09-23 22:55:13 +00:00

Conversation 0 Commits 1 Files Changed 1

+9 -1

1 Commits

Author	SHA1	Message	Date
rootiest	028478940f	ci: push docs-regen commit with a real account token, not the default bot ... The default `secrets.GITEA_TOKEN` is Gitea Actions' built-in synthetic bot identity, not a whitelistable user account. main's branch protection rejects its pushes outright regardless of retries (run 983, run 990) -- the retry/rebase loop in the next step was built for a non-fast-forward race (run 976), not a bare permission rejection, so it can't recover from this. Point the docs job's checkout token at BOT_PUSH_TOKEN, a PAT on the already-bypass-whitelisted rootiest account, so the later push succeeds. Commit authorship and GPG signing (fishconfig-bot) are set separately via git config a few steps later and are unaffected -- push auth and commit identity are independent.	2026-09-23 18:50:30 -04:00