fix(cli): correct REQUIRED_CONTEXTS context names in merge queue workflow #12

Closed
sdk-dev wants to merge 2 commits from fix/merge-queue-required-contexts-cli into main

2 Commits

Author SHA1 Message Date
sdk-dev d353a15a66 fix(cli): correct merge-queue contexts and ci.yml/release.yml path filters
CI / Test / test (pull_request) Successful in 8m12s
Release Go binaries / test (pull_request) Successful in 8m25s
[Do] Merge queue: CI checks green, merge queue ready
sop-checklist / all-items-acked SOP checklist acknowledged
Release Go binaries / release (pull_request) Has been skipped
Two separate issues fixed together:

1. gitea-merge-queue.yml REQUIRED_CONTEXTS: CI workflow posts
   "CI / Test / test (pull_request)" — the workflow triggers on
   pull_request events so Gitea uses "(pull_request)" suffix (not
   "(push)" as was previously documented).

2. ci.yml and release.yml path filters: the post-suspension sweep
   renamed .github/workflows/ → .gitea/workflows/ but the path
   filters inside both files still referenced .github/workflows/.
   Corrected to .gitea/workflows/ so the CI actually runs on
   subsequent PRs touching workflow files.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-16 19:22:41 +00:00
sdk-dev d576640a25 fix(cli): correct REQUIRED_CONTEXTS context names in merge queue workflow
sop-checklist / all-items-acked SOP checklist acknowledged by sdk-dev
The workflow override set REQUIRED_CONTEXTS=CI / test (pull_request),
but Gitea's status API reports contexts as "CI / Test / test (push)"
for cron-triggered/scheduled runs. This mismatch caused the queue script
to always see the context as "missing" and never attempt a merge.

Fix: update REQUIRED_CONTEXTS to the live API-reported context name
"CI / Test / test (push)" and restore the SOP checklist gate context
(dropped when the workflow overrode the script defaults).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-16 18:11:22 +00:00