Merge main into release/6.3
#1147
Draft
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
The Contributor Experience Workgroup is currently formalizing the Code Owner role and as part of that standardizes the definition of code owners in a .github/CODEOWNERS file across the swiftlang organization (swiftlang/swift-org-website#1269). Move the existing `CODEOWNERS` file at the root of the repository into the `.github` folder to reflect this standard.
…#1133) * Add configuration to disable ordered imports grouping * Fix issues raised in PR comments - Improve config naming for clarity. - Remove special array for combined import types. - Undo unrelated code style change. - Add a test and fix logic issues discovered by new test. * Run swift format on changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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 PR was automatically opened by a GitHub action. Review the changes included in this PR and determine if they should be included in the release branch. If yes, merge the PR. Otherwise revert changes that should not be included on this branch.