Skip to content

Conversation

@ahoppen
Copy link
Member

@ahoppen ahoppen commented Apr 10, 2025

The typical use case for this is in the first period after Swift has cut release branches. Some repositories want to include most changes from main also in the release branch. When this job is set up, it can automatically create PRs to merge main into the release branch. Maintainers of the package can then inspect the changes to ensure that they are not too risky for the release branch. We will also run the normal PR testing on these changes, ensuring that these modifications don't break the build.

…a release branch

The typical use case for this is in the first period after Swift has cut release branches. Some repositories want to include most changes from `main` also in the release branch. When this job is set up, it can automatically create PRs to merge `main` into the release branch. Maintainers of the package can then inspect the changes to ensure that they are not too risky for the release branch. We will also run the normal PR testing on these changes, ensuring that these modifications don't break the build.
@ahoppen ahoppen requested a review from a team as a code owner April 10, 2025 15:36
ahoppen added a commit to ahoppen/swift-format that referenced this pull request Apr 10, 2025
Use workflow added by swiftlang/github-workflows#112 to create auto merge PR that merges `main` into `release/6.2`.
@ahoppen ahoppen merged commit 416e29a into swiftlang:main Apr 10, 2025
25 of 26 checks passed
@ahoppen ahoppen deleted the auto-merge branch April 10, 2025 15:55
ahoppen added a commit to ahoppen/swift-format that referenced this pull request Apr 10, 2025
Use workflow added by swiftlang/github-workflows#112 to create auto merge PR that merges `main` into `release/6.2`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants