Repository navigation
ci(merge-queue): validate queued main candidates - #68
Merged
Merged
Conversation
nick2781
enabled auto-merge (squash)
October 16, 2026 10:29
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.
Enable CI for GitHub merge-queue candidates so queued changes can be tested with the latest main and preceding entries before squash merging. Keep the existing matrix, required aggregate, permissions, concurrency and job timeouts unchanged.
Add a regression that invokes the real change-scope classifier with a documentation-only merge-group event and requires the complete check plan. The gate still rejects failed, cancelled or unexpectedly skipped jobs.
Include the contribution rules from #61, preserving Conventional Commits, standard branch names, formatting and verification requirements, and align their merge instructions with queue-candidate validation. This supersedes the separate rules-only PR without losing its scope.
Validation: 34 native Node tests pass; YAML 1.2 parsing rejects duplicate keys, and removing the new trigger leaves the original workflow structure unchanged. Queue activation follows acceptance of this workflow on main; the proposed rules retain existing branch protection, require ALLGREEN, use SQUASH and merge one eligible PR at a time.