Push ELO refresh with the PAT so it triggers the 40k deploy
actions/checkout persists GITEA_TOKEN as an http.extraheader, which takes precedence over the token in the remote URL. Gitea doesn't fire workflows for pushes made with GITEA_TOKEN, so the refreshed data never deployed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -13,6 +13,10 @@ jobs:
|
|||||||
runs-on: host
|
runs-on: host
|
||||||
steps:
|
steps:
|
||||||
- uses: actions/checkout@v4
|
- uses: actions/checkout@v4
|
||||||
|
with:
|
||||||
|
# Otherwise checkout's GITEA_TOKEN auth header overrides the PAT in the
|
||||||
|
# push URL, and Gitea won't trigger the deploy for a bot-token push.
|
||||||
|
persist-credentials: false
|
||||||
- name: Refresh ELO data
|
- name: Refresh ELO data
|
||||||
working-directory: sites/40k-rankings/statcheck-elo-scraper
|
working-directory: sites/40k-rankings/statcheck-elo-scraper
|
||||||
run: python3 refresh_elo.py
|
run: python3 refresh_elo.py
|
||||||
|
|||||||
Reference in New Issue
Block a user