Revert merge_group CI triggers: merge queue unavailable on this repo - #194
Merged
Conversation
Merge queue can't be enabled on this repo (private + user-owned; GitHub gates the feature to public repos and org-owned repos on Team/Enterprise), so the merge_group triggers added in #183 are dead config that no queue will ever fire. Restore ci.yml and secret-scan.yml to their pre-#183 state, which also drops the now-unnecessary gitleaks merge_group guard. The strict up-to-date ruleset policy has been reverted to OFF separately, returning to the velocity-friendly setup that suits this high-churn repo. Required checks (verify, Gitleaks, ui-smoke) remain enforced. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.
4 tasks
BigSimmo pushed a commit
that referenced
this pull request
Aug 14, 2026
…merged #215, #210, and #293 were queued as `done` in this same PR, each citing a PR (#1949, #1953, #1962) that turned out still to be open, not merged — verified by checking whether each PR's actual file change is present on origin/main (none are). Reconciling the original `done` requests would have closed these rows while their fixes exist only on unmerged branches, one of which (#1949) currently has failing required CI. Converts all three to `update` requests documenting the correction and the real current state, so reconciling this PR now cannot close a row before its fix has actually landed. Leaves #98, #189, and #194 as `done` unchanged — those cite PR #1950 and PR #1947, both confirmed merged into main.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reverts the
merge_groupworkflow triggers added in #183. A GitHub merge queue cannot be enabled on this repository — it's private and owned by a personal account, and GitHub gates merge queue to public repos and organization-owned repos on Team/Enterprise (the API rejects themerge_queueruleset rule with a validation error). That makes themerge_grouptriggers dead config no queue will ever fire, so this restoresci.ymlandsecret-scan.ymlto their pre-#183 state (also dropping the now-unnecessary gitleaksmerge_groupguard).Paired change (already applied, not in this diff): the strict up-to-date ruleset policy (
strict_required_status_checks_policy) has been reverted to OFF, back to the velocity-friendly setup that suits this high-churn multi-agent repo. Required checks —verify,Gitleaks,ui-smoke— remain enforced.Verification
merge_groupremoved fromonScan for secretsverify:ui— N/A: CI-config onlyClinical Governance Preflight
N/A — CI workflow triggers only; no ingestion, answer-generation, search, source, access, privacy, or clinical-output change.
Notes
merge_queueruleset rule) can be reintroduced.🤖 Generated with Claude Code