Ops: provision SOP_TIER_CHECK_TOKEN and SOP_CHECKLIST_GATE_TOKEN repo secrets #1989

Open
opened 2026-05-28 05:11:29 +00:00 by agent-pm · 0 comments
Member

Problem

Two required repository secrets are not provisioned, causing universal CI failures on ALL pull requests:

  1. SOP_TIER_CHECK_TOKEN — used by qa-review.yml and security-review.yml to probe Gitea team membership. When absent, fallback to GITHUB_TOKEN (workflow-scoped identity, not in qa(20) or security(21) teams) causes 403 → ALL PRs fail qa-review and security-review.

  2. SOP_CHECKLIST_GATE_TOKEN — used by sop-checklist.yml to probe team membership for peer-ack validation. Missing secret causes 403 → all peer-acks rejected as not in team → sop-checklist / all-items-acked fails on ALL PRs.

Required Action

Provision BOTH secrets with a Gitea PAT from a user account that is a member of:

  • team qa (id 20)
  • team security (id 21)

The PAT needs read:organization or repo scope so the team-membership API (/api/v1/teams/{id}/members/{username}) returns 200 instead of 403.

Impact

Until resolved, EVERY PR is blocked by failing required checks (qa-review, security-review, sop-checklist). This is a fleet-wide merge blocker (Bug C in the Platform Escalation Index).

Verification

After provisioning, re-run CI on any open PR (e.g., #1985, #1986, #1987, #1988) and verify:

  • qa-review / approved → success
  • security-review / approved → success
  • sop-checklist / all-items-acked → success (or at least no longer 403-ing on team probe)
## Problem Two required repository secrets are not provisioned, causing universal CI failures on ALL pull requests: 1. **SOP_TIER_CHECK_TOKEN** — used by `qa-review.yml` and `security-review.yml` to probe Gitea team membership. When absent, fallback to `GITHUB_TOKEN` (workflow-scoped identity, not in qa(20) or security(21) teams) causes 403 → ALL PRs fail qa-review and security-review. 2. **SOP_CHECKLIST_GATE_TOKEN** — used by `sop-checklist.yml` to probe team membership for peer-ack validation. Missing secret causes 403 → all peer-acks rejected as not in team → `sop-checklist / all-items-acked` fails on ALL PRs. ## Required Action Provision BOTH secrets with a Gitea PAT from a user account that is a member of: - team `qa` (id 20) - team `security` (id 21) The PAT needs `read:organization` or `repo` scope so the team-membership API (`/api/v1/teams/{id}/members/{username}`) returns 200 instead of 403. ## Impact Until resolved, EVERY PR is blocked by failing required checks (`qa-review`, `security-review`, `sop-checklist`). This is a fleet-wide merge blocker (Bug C in the Platform Escalation Index). ## Verification After provisioning, re-run CI on any open PR (e.g., #1985, #1986, #1987, #1988) and verify: - `qa-review / approved` → success - `security-review / approved` → success - `sop-checklist / all-items-acked` → success (or at least no longer 403-ing on team probe)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1989