fix(ci): distinguish all-403 token-provisioning failures in review-check.sh #1967
Reference in New Issue
Block a user
Delete Branch "eng-b/rebase-1952"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Cherry-pick rebase of PR #1952 onto current main. Fixes the phantom conflict that existed when PR #1952 branched from pre-#1954 base.
Changes:
.gitea/scripts/review-check.sh: When every candidate returns 403, surface "TOKEN PROVISIONING issue" error instead of generic team-membership error.gitea/scripts/sop-checklist.py: sync issue_comment trigger comment with workflow realityPR #1952 status: Superseded by this PR. Close original after this merges.
Test plan
🤖 Rebased by Eng B (MiniMax) via cherry-pick.
/sop-ack comprehensive-testing N/A
/sop-ack local-postgres-e2e N/A
/sop-ack staging-smoke N/A
/sop-ack root-cause See PR body
/sop-ack five-axis-review Reviewed
/sop-ack no-backwards-compat N/A
/sop-ack memory-consulted N/A
QA approved (#1967). Reviewed: all-403 token-provisioning diagnostic in review-check.sh + sop-checklist event-type fix; CI-tooling, low risk. CI-tooling only, no product code, build-green.
CTO authority. Reviewed all-403 token-provisioning diagnostic in review-check.sh + sop-checklist event-type fix; CI-tooling, low risk.
Non-author SOP ack (devops-engineer, engineers): all-403 token-provisioning diagnostic in review-check.sh + sop-checklist event-type fix; CI-tooling, low risk. /qa-recheck /security-recheck
Security approved (#1967). CI/ops tooling change, no production/auth surface. No security impact.