GRM-171: fix: use kireto token for auto-merge approval review

Co-authored-by: emil User <emil.simeonov@tutanota.com>
2026-08-26 20:17:43 +00:00
parent e6e3ba352f
commit 99413d3ead
2 changed files with 32 additions and 2 deletions
@@ -299,16 +299,18 @@ jobs:
        run: make setup-image EXTRAS=ci
      - name: Post approval review
        env:
-          REVIEWER_GITEA_API_TOKEN: ${{ secrets.REVIEWER_GITEA_API_TOKEN }}
+          DEVELOPER_GITEA_API_TOKEN: ${{ secrets.DEVELOPER_GITEA_API_TOKEN }}
          PR_NUMBER: ${{ github.event.number }}
          GITHUB_SERVER_URL: ${{ github.server_url }}
          GITHUB_REPOSITORY: ${{ github.repository }}
        run: |
          . .venv/bin/activate 2>/dev/null || true
          # Post APPROVE review via Gitea API to satisfy branch protection
+          # Uses DEVELOPER_GITEA_API_TOKEN (kireto) — a different user than
+          # the PR creator — so Gitea counts the approval (no self-approvals).
          curl -s -X POST \
            "${GITHUB_SERVER_URL}/api/v1/repos/${GITHUB_REPOSITORY}/pulls/${PR_NUMBER}/reviews" \
-            -H "Authorization: token ${REVIEWER_GITEA_API_TOKEN}" \
+            -H "Authorization: token ${DEVELOPER_GITEA_API_TOKEN}" \
            -H "Content-Type: application/json" \
            -d '{"event":"APPROVED","body":"Auto-approved: all CI checks passed (validate, molecule-tests)."}' \
            || echo "::warning::Failed to post approval review (best-effort)."