Repository navigation
ci: main-only workflow triggers, cancel-in-progress everywhere - #2630
Conversation
Drew's order 2026-10-30: CI runs only on the main branch. - push triggers restricted to branches: [main] (tag-only release triggers and paths filters kept as-is) - pull_request / pull_request_target triggers removed everywhere - every workflow's concurrency now sets cancel-in-progress: true (groups unchanged); concurrency block added where missing - schedule, workflow_dispatch, workflow_run, merge_group and other non-branch triggers unchanged
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 38 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Drew's CI policy (2026-10-30): workflows run only on main. Feature-branch and pull-request CI is disabled; every workflow gets cancel-in-progress concurrency.
pushrestricted tobranches: [main]everywhere (they already were in this repo; tag-only release trigger in goreleaser kept untouched, paths filters kept)pull_requesttriggers removed from 13 workflows (cf-container-hello, go-modules-build, id-check, identity-build, lab-ops-hub, map-build, mcpx-conformance, mcpx-nixbuild, mcpx, mod-tidy, nix-ci, research-workflow, +1)cancel-in-progress: trueset on every workflow (several scheduled workflows hadfalse; flipped per the blanket order); concurrency block added to jules.ymlMerging immediately per Drew's standing merge authority — PRs no longer receive CI under this policy.
Need help on this PR? Tag
@codesmith-botwith what you need.