PRs #516 and #530 removed the pull_request trigger from e2e-staging-saas
to prevent double fires on provisioning-critical PR pushes. This caused a
merge deadlock: branch protection requires status checks on every PR, but
push-only workflows don't fire on PR branches, leaving required checks
absent → Gitea blocks merge even though CI itself is green.
Fix: restore pull_request trigger (branch protection needs status on every
PR) and split the job into:
- pr-validate: always posts success for pull_request paths
(best-effort steps, continue-on-error: true — runner issues must not
block merge)
- e2e-staging-saas: guarded with
`if: github.event.pull_request.base.ref == ''` so it only runs on
trunk pushes, avoiding the double-fire that motivated the removal
The gate-check-v3.yml workflow_dispatch.inputs removal from PRs #516/#530
is preserved unchanged.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Issue #504: e2e-staging-saas.yml had BOTH push:[main] + pull_request:[main].
This caused the full 25-35 min staging provision+teardown cycle to fire on
every PR push to main (in addition to the push trigger). The pull_request
trigger is removed — branch protection ensures only merged code reaches
main, so push:[main] is sufficient. Pre-merge E2E for provisioning paths
is better served by local harness-replays.yml (which stays push+pull_request).
Issue #419: gate-check-v3.yml had workflow_dispatch.inputs which Gitea
1.22.6 parser rejects with "unknown on type" (it mis-treats the inputs
sub-keys as top-level on: event types). The entire workflow was silently
ignored. Dropping the inputs block restores parsing. Manual dispatch from
the Gitea UI works without the schema (github.event.inputs.X returns
empty; the script iterates all open PRs when PR_NUMBER is empty).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
