Skip to content

ci: remove push/pull_request workflow triggers - #5501

Merged
developing-today[bot] merged 1 commit into
mainfrom
chore/no-push-pr-triggers
Nov 4, 2026
Merged

developing-today[bot] merged 1 commit into
mainfrom
chore/no-push-pr-triggers

Conversation

@developing-today

@developing-today developing-today Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Per Drew'''s ruling (2026-11-04): no commit- or PR-triggered CI — CI runs via dispatch/placement, schedule, and workflow_call only.

Removes every push: and pull_request:/pull_request_target: entry from the on: block of the workflows below. All other triggers (schedule, workflow_dispatch, workflow_call, release, merge_group, workflow_run, issue_comment) are unchanged, and nothing outside the on: blocks is touched.

Files changed:

  • .github/workflows/cf-container-hello.yml
  • .github/workflows/cold-store-reaper.yml
  • .github/workflows/go-modules-build.yml
  • .github/workflows/goreleaser.yml
  • .github/workflows/id-bench.yml
  • .github/workflows/id-check.yml
  • .github/workflows/identity-build.yml
  • .github/workflows/lab-ops-hub.yml
  • .github/workflows/map-build.yml
  • .github/workflows/mcpx-conformance.yml
  • .github/workflows/mcpx-docs.yml
  • .github/workflows/mcpx-fix-test-guard.yml
  • .github/workflows/mcpx-nixbuild.yml
  • .github/workflows/mcpx-release.yml
  • .github/workflows/mcpx-test.yml
  • .github/workflows/mcpx-tier2-containers.yml
  • .github/workflows/mcpx.yml
  • .github/workflows/nix-ci.yml
  • .github/workflows/opencode-config-guard.yml
  • .github/workflows/pm-aggregator-tests.yml
  • .github/workflows/pm-stack-tests.yml
  • .github/workflows/production-line-guard.yml
  • .github/workflows/proxy-port-fallbacks.yml
  • .github/workflows/research-workflow.yml
  • .github/workflows/scripts-test.yml

Note: proxy-port-fallbacks.yml had only pull_request + merge_group triggers; it is now merge_group-only (no workflow_dispatch added) — flagged for review. opencode-config-guard.yml keeps merge_group + workflow_dispatch.


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

@developing-today
developing-today Bot requested review from a team and dezren39 as code owners November 4, 2026 14:27
@developing-today
developing-today Bot merged commit 59e4282 into main Nov 4, 2026
@developing-today
developing-today Bot deleted the chore/no-push-pr-triggers branch November 4, 2026 14:27
@coderabbitai

coderabbitai Bot commented Nov 4, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 7997b73a-2f84-4366-ae7f-c1e27c1832d1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Share

dezren39 pushed a commit that referenced this pull request Nov 4, 2026
ci-policy.md still claimed a basic PR tier, a required proxy check and a
merge queue; #5501 removed every push/pull_request trigger by owner
ruling. Rewrite the policy around what actually runs, record that branch
protection and rulesets name no required checks, and list the inert
PR-only code left for a reviewed cleanup.

Update the AGENTS.md pointer so workers read the current trigger model
instead of a merge gate that no longer exists.

Refs #5149, #4533.
dezren39 pushed a commit that referenced this pull request Nov 4, 2026
Update the stale PR-tier/merge-queue claims to the current owner
ruling: workflow verification is dispatch/schedule plus the remaining
explicit event triggers, and there is no configured Actions merge gate.
Keep the change classes advisory, not a claim of automatic coverage.

Remove the redundant PR-exclusion conditions that are always true for
the remaining schedule/dispatch events. Preserve payload-sensitive
PR-only steps. No tests or check bodies are changed.

Refs #5149, #4533.
@dezren39

dezren39 commented Nov 5, 2026

Copy link
Copy Markdown
Member

🤖 Agent note · bound

@dezren39 dezren39 added queue/queued Has a queued task in the Supabase agent queue status/needs-triage Not yet triaged; needs a first look labels Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

queue/queued Has a queued task in the Supabase agent queue status/needs-triage Not yet triaged; needs a first look

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant