Run the gate on the pull request, and CI on pull requests and main only #112

Merged
cruelacid merged 1 commit from worktree-pr-gate into main 2026-09-23 14:52:21 +01:00
Owner

Closes #80. Part of #77.

  • on: is now push: branches: [main] plus pull_request:, so a PR no longer runs CI twice. A branch with no PR gets no CI, deliberately.
  • e2e runs on pull_request as well as on main. promote stays main only, so :stable still moves only after a green gate in its own run on the deployed sha.
  • The comment keeps the history of main-only CI never running, and says why this shape does not repeat it.
  • docs/releasing.md, "The pipeline", is updated to match.

This is the first real pull request merged onto main. Its run records the status-context names that #79's branch protection will require.

Changelog

NONE

🤖 Generated with Claude Code

https://claude.ai/code/session_01StURdiv33xnMfE2XRyg8Lt

Closes #80. Part of #77. - `on:` is now `push: branches: [main]` plus `pull_request:`, so a PR no longer runs CI twice. A branch with no PR gets no CI, deliberately. - `e2e` runs on `pull_request` as well as on `main`. `promote` stays `main` only, so `:stable` still moves only after a green gate in its own run on the deployed sha. - The comment keeps the history of main-only CI never running, and says why this shape does not repeat it. - `docs/releasing.md`, "The pipeline", is updated to match. This is the first real pull request merged onto `main`. Its run records the status-context names that #79's branch protection will require. ## Changelog NONE 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01StURdiv33xnMfE2XRyg8Lt
Run the gate on the pull request, and CI on pull requests and main only
All checks were successful
CI / build (pull_request) Successful in 4m24s
CI / e2e (pull_request) Successful in 4m38s
CI / promote (pull_request) Has been skipped
CI / build (push) Successful in 4m54s
CI / e2e (push) Successful in 4m50s
CI / promote (push) Successful in 31s
796d6170c7
push and pull_request fired on the same sha, so every pull request ran CI
twice. push is now main only, and a branch asks for CI by opening a pull
request. e2e runs on the pull request as well as on main, so a red suite
means "do not merge" rather than "main is already broken and the deploy was
stopped after the fact". promote stays main only.

Part of #77. Closes #80.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01StURdiv33xnMfE2XRyg8Lt
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Nectenda/nectenda!112
No description provided.