Repository navigation
ci(mergify): remove obsolete queue configuration - #353
Merged
loveRhythm1990 merged 3 commits intoOct 21, 2026
Merged
loveRhythm1990 merged 3 commits into
loveRhythm1990 merged 3 commits into
Conversation
Collaborator
Author
|
lgtm |
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
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.
What type of PR is this?
What this PR does / why we need it
Behavior change: this proposal restores valid configuration, but does not restore automatic enqueueing with the currently reported product settings. Maintainers would use
@mergifyio queue. The enqueueing policy needs a maintainer decision before merge.Remove rejected
queue_rules[].autoqueueand migratecommit_message_templatetocommit_message_format. Keep one approval, nodo-not-merge, andbase=mainas queue-level conditions. Squash merging, timeout, concurrency, and GitHub branch protection remain unchanged. Approver attribution becomes standardApproved-bytrailers.Related: #285; configuration failures on #347, #348, and #350.
Enqueueing decision
Automatic: enable Merge Protections in the dashboard, then explicitly configure a conditional list (not unconditional
true):This is an alternative, not included in the patch. Once
autoqueueis removed, do not rely on the bot to migrate that field automatically.Manual: accept this proposal and use
@mergifyio queuefor eligible PRs.The live configuration check confirms Workflow Automation is disabled, so the retained
pull_request_rulesare inactive; this is now documented inline. The Merge Protections prerequisite comes from the bot's #285 notice; dashboard settings have not been independently verified or changed.Validation
git diff --checkpassed.Configuration changedpassed on999ccb4; the latest commit only adds comments and parses identically. Latest-head CI is pending..mergify.ymlwere found.Mergify Merge Queuestill evaluates main's old configuration until merge, so itsautoqueueerror is separate from proposed-file validation.Only
.mergify.ymlchanges. No merge or product-setting changes performed.