Update automergers for late release cycle #1436
Merged
Conversation
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
Contributor
Author
|
@swift-ci please test |
parkera
approved these changes
Jul 15, 2025
Contributor
parkera
left a comment
parkera
left a comment
There was a problem hiding this comment.
Looks good to me conceptually but I'll leave verifying the details to someone who knows more than I do about the system.
itingliu
approved these changes
Jul 15, 2025
This was referenced Jul 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This adds a new auto merger to the repo that merges forwards from the release/6.2 branch to main. We will use this during the later period of a release cycle (instead of the existing backwards auto merger from main to release/6.2) to include all PRs merged to release branches on main automatically to avoid the need for cherry-picks.