fix(ci): use GITOPS_PAT instead of never-configured GITOPS_PUSH_TOKEN
All checks were successful
build-and-release / build (catering-services) (push) Successful in 49s
build-and-release / build (cron) (push) Successful in 49s
build-and-release / build (developers) (push) Successful in 39s
build-and-release / build (employees) (push) Successful in 38s
build-and-release / build (fitness-trainers) (push) Successful in 38s
build-and-release / build (gateway) (push) Successful in 38s
build-and-release / build (graphic-designers) (push) Successful in 38s
build-and-release / build (job-seekers) (push) Successful in 39s
build-and-release / build (jobs) (push) Successful in 39s
build-and-release / build (leads) (push) Successful in 39s
build-and-release / build (makeup-artists) (push) Successful in 39s
build-and-release / build (companies) (push) Successful in 6m56s
build-and-release / build (payments) (push) Successful in 39s
build-and-release / build (customers) (push) Successful in 6m33s
build-and-release / build (social-media-managers) (push) Successful in 39s
build-and-release / build (ugc-content-creators) (push) Successful in 39s
build-and-release / build (users) (push) Successful in 39s
build-and-release / build (video-editors) (push) Successful in 39s
build-and-release / build (photographers) (push) Successful in 6m28s
build-and-release / build (tutors) (push) Successful in 6m32s

Confirmed via the matrix run: every service's actual docker build and
push succeeded, but the GitOps-update step failed on all of them with
"GITOPS_PUSH_TOKEN is empty". Checked the repo's configured secrets -
GITOPS_PUSH_USERNAME/GITOPS_PUSH_TOKEN were never set; only a leftover
GITOPS_GITHUB_USERNAME/GITOPS_GITHUB_TOKEN pair (from before the
gitops repo moved to Forgejo) and GITOPS_PAT exist. Confirmed
ashwin/nxtgauge-gitops lives on ci.nxtgauge.com matching this
workflow's defaults, so GITOPS_PAT is the one meant for this.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Ashwin Kumar Sivakumar 2026-07-08 02:10:33 +05:30
parent e8651cf6c6
commit 9efb733974

View file

@ -156,15 +156,19 @@ jobs:
GITOPS_OWNER: ${{ secrets.GITOPS_OWNER || 'ashwin' }}
GITOPS_REPO: ${{ secrets.GITOPS_REPO || 'nxtgauge-gitops' }}
GITOPS_BRANCH: ${{ secrets.GITOPS_BRANCH || 'main' }}
GITOPS_PUSH_USERNAME: ${{ secrets.GITOPS_PUSH_USERNAME }}
GITOPS_PUSH_TOKEN: ${{ secrets.GITOPS_PUSH_TOKEN }}
# The gitops repo now lives on Forgejo (ci.nxtgauge.com), not
# GitHub - GITOPS_PUSH_USERNAME/GITOPS_PUSH_TOKEN were never
# actually configured as repo secrets (only the leftover
# GITOPS_GITHUB_* pair and GITOPS_PAT exist). Use GITOPS_PAT,
# which matches the current Forgejo-hosted repo.
GITOPS_PAT: ${{ secrets.GITOPS_PAT }}
SHA: ${{ github.sha }}
run: |
set -euo pipefail
test -n "${GITOPS_PUSH_TOKEN:-}" || { echo "GITOPS_PUSH_TOKEN is empty"; exit 1; }
test -n "${GITOPS_PAT:-}" || { echo "GITOPS_PAT is empty"; exit 1; }
service="${{ matrix.service }}"
git clone "https://${GITOPS_PUSH_USERNAME}:${GITOPS_PUSH_TOKEN}@${GITOPS_SERVER}/${GITOPS_OWNER}/${GITOPS_REPO}.git" /tmp/nxtgauge-gitops
git clone "https://forgejo-actions:${GITOPS_PAT}@${GITOPS_SERVER}/${GITOPS_OWNER}/${GITOPS_REPO}.git" /tmp/nxtgauge-gitops
cd /tmp/nxtgauge-gitops
# Up to 3 of these jobs can be pushing to the same gitops branch at