ci: avoid redundant post-merge runs - #3203
Merged
Merged
Conversation
Merge queue checks already validate the final combined change before it lands, so stop rerunning required workflows on main after merge. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
because we have merge queue now, we dont need to check it again on |
kevinjqliu
force-pushed
the
kevinjqliu-optimize-merge-queue
branch
2 times, most recently
from
September 11, 2026 23:49
0bbc716 to
859dea4
Compare
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.
Which issue does this PR close?
What changes are included in this PR?
Remove
mainpush triggers from required workflows. The merge queue already runs the same checks against the final combined change.Are these changes tested?
Checked with actionlint.
AI Disclosure
Written with GitHub Copilot, reviewed by me.