ci: drop the unused merge queue trigger from Fork CI - #119
Merged
Conversation
The merge queue was retired as duplicated CI work, so the merge_group trigger and its base_sha/head_sha fallbacks are dead config. Pull request and push events resolve the same SHAs without them.
github-actions
Bot
added
vouch:trusted
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 13, 2026
## Problem The merge queue was retired because it duplicated CI work, but Fork CI still carries its plumbing: a `merge_group` trigger and `github.event.merge_group.*` fallbacks in the `changes` job's SHA resolution. Nothing fires it, so it is dead config that implies a workflow the repo no longer uses. ## Fix Remove the trigger and the two fallbacks. `pull_request` and `push` events already resolve the same SHAs on their own: - `BASE_SHA` → `pull_request.base.sha` or `github.event.before` - `HEAD_SHA` → `pull_request.head.sha` or `github.sha` ## Verification Confirmed no merge queue is configured, so nothing is stranded by this: - The `PR + CI` ruleset on `main` contains only `pull_request` and `required_status_checks` rules — no `merge_queue` rule. - All four required checks (`Fork Changes`, `Fork Check`, `Fork Release Smoke`, `Fork Test`) run on `pull_request`, so they still report on every PR. Workflow parses and `actionlint` reports no new findings. Follow-up to #112. --- Written by an agent (Claude Code, claude-opus-5).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 13, 2026
## Problem The merge queue was retired because it duplicated CI work, but Fork CI still carries its plumbing: a `merge_group` trigger and `github.event.merge_group.*` fallbacks in the `changes` job's SHA resolution. Nothing fires it, so it is dead config that implies a workflow the repo no longer uses. ## Fix Remove the trigger and the two fallbacks. `pull_request` and `push` events already resolve the same SHAs on their own: - `BASE_SHA` → `pull_request.base.sha` or `github.event.before` - `HEAD_SHA` → `pull_request.head.sha` or `github.sha` ## Verification Confirmed no merge queue is configured, so nothing is stranded by this: - The `PR + CI` ruleset on `main` contains only `pull_request` and `required_status_checks` rules — no `merge_queue` rule. - All four required checks (`Fork Changes`, `Fork Check`, `Fork Release Smoke`, `Fork Test`) run on `pull_request`, so they still report on every PR. Workflow parses and `actionlint` reports no new findings. Follow-up to #112. --- Written by an agent (Claude Code, claude-opus-5).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 14, 2026
## Problem The merge queue was retired because it duplicated CI work, but Fork CI still carries its plumbing: a `merge_group` trigger and `github.event.merge_group.*` fallbacks in the `changes` job's SHA resolution. Nothing fires it, so it is dead config that implies a workflow the repo no longer uses. ## Fix Remove the trigger and the two fallbacks. `pull_request` and `push` events already resolve the same SHAs on their own: - `BASE_SHA` → `pull_request.base.sha` or `github.event.before` - `HEAD_SHA` → `pull_request.head.sha` or `github.sha` ## Verification Confirmed no merge queue is configured, so nothing is stranded by this: - The `PR + CI` ruleset on `main` contains only `pull_request` and `required_status_checks` rules — no `merge_queue` rule. - All four required checks (`Fork Changes`, `Fork Check`, `Fork Release Smoke`, `Fork Test`) run on `pull_request`, so they still report on every PR. Workflow parses and `actionlint` reports no new findings. Follow-up to #112. --- Written by an agent (Claude Code, claude-opus-5).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 14, 2026
## Problem The merge queue was retired because it duplicated CI work, but Fork CI still carries its plumbing: a `merge_group` trigger and `github.event.merge_group.*` fallbacks in the `changes` job's SHA resolution. Nothing fires it, so it is dead config that implies a workflow the repo no longer uses. ## Fix Remove the trigger and the two fallbacks. `pull_request` and `push` events already resolve the same SHAs on their own: - `BASE_SHA` → `pull_request.base.sha` or `github.event.before` - `HEAD_SHA` → `pull_request.head.sha` or `github.sha` ## Verification Confirmed no merge queue is configured, so nothing is stranded by this: - The `PR + CI` ruleset on `main` contains only `pull_request` and `required_status_checks` rules — no `merge_queue` rule. - All four required checks (`Fork Changes`, `Fork Check`, `Fork Release Smoke`, `Fork Test`) run on `pull_request`, so they still report on every PR. Workflow parses and `actionlint` reports no new findings. Follow-up to #112. --- Written by an agent (Claude Code, claude-opus-5).
incognitojam
added a commit
that referenced
this pull request
Aug 15, 2026
## Problem The merge queue was retired because it duplicated CI work, but Fork CI still carries its plumbing: a `merge_group` trigger and `github.event.merge_group.*` fallbacks in the `changes` job's SHA resolution. Nothing fires it, so it is dead config that implies a workflow the repo no longer uses. ## Fix Remove the trigger and the two fallbacks. `pull_request` and `push` events already resolve the same SHAs on their own: - `BASE_SHA` → `pull_request.base.sha` or `github.event.before` - `HEAD_SHA` → `pull_request.head.sha` or `github.sha` ## Verification Confirmed no merge queue is configured, so nothing is stranded by this: - The `PR + CI` ruleset on `main` contains only `pull_request` and `required_status_checks` rules — no `merge_queue` rule. - All four required checks (`Fork Changes`, `Fork Check`, `Fork Release Smoke`, `Fork Test`) run on `pull_request`, so they still report on every PR. Workflow parses and `actionlint` reports no new findings. Follow-up to #112. --- Written by an agent (Claude Code, claude-opus-5).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 18, 2026
## Problem The merge queue was retired because it duplicated CI work, but Fork CI still carries its plumbing: a `merge_group` trigger and `github.event.merge_group.*` fallbacks in the `changes` job's SHA resolution. Nothing fires it, so it is dead config that implies a workflow the repo no longer uses. ## Fix Remove the trigger and the two fallbacks. `pull_request` and `push` events already resolve the same SHAs on their own: - `BASE_SHA` → `pull_request.base.sha` or `github.event.before` - `HEAD_SHA` → `pull_request.head.sha` or `github.sha` ## Verification Confirmed no merge queue is configured, so nothing is stranded by this: - The `PR + CI` ruleset on `main` contains only `pull_request` and `required_status_checks` rules — no `merge_queue` rule. - All four required checks (`Fork Changes`, `Fork Check`, `Fork Release Smoke`, `Fork Test`) run on `pull_request`, so they still report on every PR. Workflow parses and `actionlint` reports no new findings. Follow-up to #112. --- Written by an agent (Claude Code, claude-opus-5).
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 free
to 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.
Problem
The merge queue was retired because it duplicated CI work, but Fork CI still
carries its plumbing: a
merge_grouptrigger andgithub.event.merge_group.*fallbacks in the
changesjob's SHA resolution. Nothing fires it, so it is deadconfig that implies a workflow the repo no longer uses.
Fix
Remove the trigger and the two fallbacks.
pull_requestandpusheventsalready resolve the same SHAs on their own:
BASE_SHA→pull_request.base.shaorgithub.event.beforeHEAD_SHA→pull_request.head.shaorgithub.shaVerification
Confirmed no merge queue is configured, so nothing is stranded by this:
PR + CIruleset onmaincontains onlypull_requestandrequired_status_checksrules — nomerge_queuerule.Fork Changes,Fork Check,Fork Release Smoke,Fork Test) run onpull_request, so they still report on every PR.Workflow parses and
actionlintreports no new findings.Follow-up to #112.
Written by an agent (Claude Code, claude-opus-5).