Fix: use GA_TOKEN for push to main (branch protection requires jmiller)
Some checks failed
Repo Health / Access control (push) Successful in 1s
Auto-Update SHA Hash / Update SHA-256 Hash in updates.xml (release) Failing after 6s
Repo Health / Release configuration (push) Failing after 3s
Repo Health / Scripts governance (push) Successful in 4s
Repo Health / Repository health (push) Failing after 4s

The default checkout token doesn't have push access to protected main.
Set remote URL with GA_TOKEN (jmiller's PAT) for authenticated push.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jonathan Miller
2026-04-18 12:31:42 -05:00
parent de5794b683
commit 799ae5f478

View File

@@ -378,6 +378,7 @@ jobs:
VERSION="${{ steps.meta.outputs.version }}"
CURRENT_BRANCH="${{ github.ref_name }}"
TOKEN="${{ secrets.GA_TOKEN }}"
TOKEN="${{ secrets.GA_TOKEN }}"
git config --local user.email "gitea-actions[bot]@mokoconsulting.tech"
git config --local user.name "gitea-actions[bot]"
@@ -385,6 +386,9 @@ jobs:
git commit -m "chore: update ${STABILITY} SHA-256 for ${VERSION} [skip ci]" \
--author="gitea-actions[bot] <gitea-actions[bot]@mokoconsulting.tech>"
# Set push URL with GA_TOKEN for authenticated pushes
git remote set-url origin "https://jmiller:${TOKEN}@git.mokoconsulting.tech/${GITEA_ORG}/${GITEA_REPO}.git"
# Push to current branch
git push || true