Skip to content

Conversation

@github-actions
Copy link

@github-actions github-actions bot commented Dec 8, 2025

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.

ahoppen and others added 16 commits November 13, 2025 09:27
…lot projects

To understand whether a PR breaks the formatting behavior of real-world code, add a GitHub action that formats a small set of pilot projects and ensures that `swift-format lint` does not produce any errors.
This change prevents the job from being triggered when `release/*`
branches are synchronized on a fork.
Skip the `update-version` job on a fork
Add GitHub workflow to ensure formatting is not broken on a set of pilot projects
* print lint location and message in plain bold instead of white

fixes #1087

* review: print source locations in plain text

Co-authored-by: Tony Allevato <[email protected]>

* swap the colors for warning labels and diagnostic categories

This aligns the color of warning labels with the Swift compiler by
making them yellow instead of magenta. Diagnostic categories were
changed to make them not share a color with the warning labels.

---------

Co-authored-by: Tony Allevato <[email protected]>
* Order conditionally-compiled imports

* Order conditional imports based on configuration and add nested test case

* Preserve comments at start of conditionally compiled block in OrderedImports

* Add includeConditionalImports docs to OrderedImports.swift
Normalize release version to x.y.z in auto-update-version action
The diff yields more insightful results than `swift-format lint`
Keep attributed getters intact in UseSingleLinePropertyGetter
Respect indentBlankLines when stripping whitespace inside block comment blank lines
Format source code and run `git diff` instead of listing first
Update release automerge from 6.2 to 6.3
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.

7 participants