Repository: nicklockwood/SwiftFormat

Stars: 8777

CLAUDE.md Copy Chapter

SwiftFormat

SwiftFormat is a code formatting tool for Swift. It applies a set of rules to Swift source files, transforming them to follow consistent style conventions.

Project Structure Copy Chapter

- Sources/Rules/ - Individual formatting rules (one file per rule)
- Tests/Rules/ - Test cases for rules
- Sources/Formatter.swift - Core formatter class with token manipulation APIs
- Sources/ParsingHelpers.swift - Parsing helpers for Swift grammar (types, declarations, expressions, etc.)
- Sources/FormattingHelpers.swift - Higher-level formatting utilities
- Sources/Options.swift - Options for configuring the behavior of individual rules
- Sources/OptionDescriptor.swift - Command line flag configuration for rule options

Branching Copy Chapter

All changes and pull requests should target the develop branch, not main.

Building and Testing Copy Chapter

Build the project

swift build
Run all tests (on macOS)

swift test
Run all tests (on Linux)

--enable-test-discovery is required because LinuxMain.swift (kept for Mint

compatibility) has an empty test list that overrides automatic discovery.

swift test --enable-test-discovery
Test a specific rule (works on both macOS and Linux)

./Scripts/test_rule.sh <ruleName>
Format the codebase (run after making changes)

./Scripts/test_rule.sh runs this automatically

./format.sh

Adding New Rules Copy Chapter

Before You Start Copy Section

Read the helper files thoroughly. Before writing any rule, familiarize yourself with the existing helpers:

- Sources/Formatter.swift - Token manipulation APIs
- Sources/ParsingHelpers.swift - Parsing helpers for types, declarations, expressions, properties, functions, etc.
- Sources/FormattingHelpers.swift - Higher-level formatting utilities
- Sources/Declarations.swift - Helpers related to individual declarations

You MUST review the APIs available in these files using:

$ rg "^    (func|var) " Sources/Formatter.swift Sources/FormattingHelpers.swift Sources/ParsingHelpers.swift Sources/Declaration.swift

Many rules can be implemented using existing helpers. Before writing custom token parsing code, verify no existing helper does what you need.

Rule File Structure Copy Section

Create a new file in Sources/Rules/ named after your rule (e.g., MyRule.swift). Rules are defined as static properties on FormatRule:

//
//  MyRule.swift
//  SwiftFormat
//
import Foundation
public extension FormatRule {
    /// Brief description of what the rule does
    static let myRule = FormatRule(
        help: "Description shown in --help output."
    ) { formatter in
        // Rule implementation goes here. For example:
        formatter.forEach(.keyword("let")) { i, _ in
            // Process each occurrence
        }
    } examples: {
        """

"""
    }
}

Rule tests are implemented in Tests/Rules/MyRuleTests.swift.

Best Practices Copy Section

- File author names: when creating new files, always use the name of the actual user / human author, and the current date. NEVER write a file header like "Created by Claude Code" or "Created by GitHub Copilot". Prefer the user's full name as opposed to just their username.
- Minimal changes only. Only modify tokens when an actual change is needed. Any modification triggers a lint error in --lint mode.
- Preserve comments. Prefer preserving code as-is if updating would require removing comments.
- Keep it simple. Write as little code as possible. If a change dramatically increases complexity, consider asking if it should be de-scoped.
- Define local helpers in extensions on Formatter at the bottom of the rule file. Mark them internal for discoverability. Move helpers used by multiple rules to ParsingHelpers.swift. Parsing code should almost always be factored out into a rule-specific helper (or later a shared helper if necessary) rather than being implemented directly in the rule implementation closure.

Always use Formatter APIs. Never manipulate token arrays directly:

// ✓ Good - use Formatter APIs
formatter.insert(.space(" "), at: index)
formatter.removeToken(at: index)
formatter.replaceToken(at: index, with: .keyword("let"))
// ✗ Bad - array manipulation
var tokens = Array(formatter.tokens[start...end])
tokens.append(.space(" "))
formatter.replaceTokens(in: start...end, with: tokens)

Never use raw index loops. Always traverse tokens using helpers:

// ✓ Good - use traversal helpers
formatter.index(of: .nonSpaceOrCommentOrLinebreak, after: i)
formatter.index(of: .keyword("func"), before: i)
formatter.endOfLine(at: i)
// ✗ Bad - raw index manipulation
while i < formatter.tokens.count { i += 1 }
for i in 0..<formatter.tokens.count { ... }

Writing Tests Copy Section

Use the testFormatting helper defined in XCTestCase extensions:

func testMyRule() {
    let input = """
        // input code
        """
    let output = """
        // expected output
        """
    testFormatting(for: input, output, rule: .myRule)
}

- Create several test scenarios covering different cases, but don't exhaustively test every configuration.
- Use testFormatting(for: input, [output], rules: [.myRule, .otherRule]) to test multiple rules together.
- Prefer formatting input and output code to match the behavior of other rules, instead of excluding other rules with exclude:. Only use exclude: if the other rule being applied directly conflicts with what the test case is trying to test.
- Do not use // MARK comments in tests.
- Always use multi-line string literals (""") for input and output code.

Debugging Copy Section

To debug a rule, run the existing tests or create new test cases. NEVER try to directly run SwiftFormat on a file via the command line.

Use print debugging as necessary to gather more context. Run individual test cases using:

On macOS:

swift test --filter <TestClassName>.<testMethodName>
On Linux (--enable-test-discovery required):

swift test --enable-test-discovery --filter <TestClassName>.<testMethodName>

After Writing the Rule Copy Section

1. Run the rule tests: ./Scripts/test_rule.sh <ruleName>
2. Run the full test suite: swift test (or swift test --enable-test-discovery on Linux)
3. [VERY IMPORTANT] Review your code - ensure it follows all best practices above
4. [VERY IMPORTANT] Simplify further - look for functionality that could be removed to reduce complexity

Note: Do not modify Rules.md directly. It's auto-generated when running the test suite. MetadataTests may fail after adding a new rule; re-run after metadata regenerates.

See Also Copy Chapter

@CONTRIBUTING.md

README.md Copy Chapter



Table of Contents
-----------------

- What?
- Why?
- How?
- Command-line tool
- Xcode source editor extension
- Xcode build phase
- Swift Package Manager plugin
- Via Applescript
- VSCode plugin
- Sublime Text plugin
- Nova plugin
- Git pre-commit hook
- GitHub Actions
- On CI using Danger
- Bazel build
- Docker
- Prerelease Builds
- Configuration
- Options
- Rules
- Swift version
- Config file
- Globs
- Linting
- Error codes
- Cache
- File headers
- Markdown formatting
- FAQ
- Known issues
- Tip Jar
- Credits

What is this?
----------------

SwiftFormat is a code library and command-line tool for reformatting Swift code on macOS, Linux or Windows.

SwiftFormat goes above and beyond what you might expect from a code formatter. In addition to adjusting white space it can insert or remove implicit self, remove redundant parentheses, and correct many other deviations from the standard Swift idioms.

Why would I want to do that?
-----------------------------

Many programmers have a preferred style for formatting their code, and others seem entirely blind to the existing formatting conventions of a project (to the enragement of their colleagues).

When collaborating on a project, it can be helpful to agree on a common coding style, but enforcing that manually is tedious and error-prone, and can lead to arguments if some participants take it more seriously than others.

Having a tool to automatically enforce a common style eliminates those issues, and lets you focus on the behavior of the code, not its presentation.

How do I install it?
---------------------

That depends - There are several ways you can use SwiftFormat:

1. As a command-line tool that you run manually, or as part of some other toolchain
2. As a Source Editor Extension that you can invoke via the Editor > SwiftFormat menu within Xcode
3. As a build phase in your Xcode project, so that it runs every time you press Cmd-R or Cmd-B, or
4. As a Git pre-commit hook, so that it runs on any files you've changed before you check them in

Command-line tool
-------------------

Installation:

You can install the swiftformat command-line tool on macOS or Linux using Homebrew. Assuming you already have Homebrew installed, just type:

$ brew install swiftformat

To update to the latest version once installed:

$ brew upgrade swiftformat

Alternatively, you can install the tool on macOS or Linux by using Mint as follows:

$ mint install nicklockwood/SwiftFormat

If you use Nix, you can add SwiftFormat to a devShell using nixpkgs:

{
  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";
  };
  outputs = { nixpkgs, ... }:
    let
      system = "aarch64-darwin";
      pkgs = import nixpkgs { inherit system; };
    in {
      devShells.${system}.default = pkgs.mkShell {
        packages = [
          pkgs.swiftformat
        ];
      };
    };
}

If you need to pin SwiftFormat to a specific version in your devShell, you can use acevif/swiftformat-nix:

{
  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";
    swiftformat-nix.url = "github:acevif/swiftformat-nix";
  };
  outputs = { nixpkgs, swiftformat-nix, ... }:
    let
      system = "aarch64-darwin";
      pkgs = import nixpkgs { inherit system; };
    in {
      devShells.${system}.default = pkgs.mkShell {
        packages = [
          swiftformat-nix.packages.${system}.swiftformat_0_58_7
        ];
      };
    };
}

Replace aarch64-darwin with your system, and replace swiftformat_0_58_7 with the version you want to install.

Or if you prefer, you can check out and build SwiftFormat manually on macOS, Linux or Windows as follows:

$ git clone https://github.com/nicklockwood/SwiftFormat
$ cd SwiftFormat
$ swift build -c release

If you are installing SwiftFormat into your project directory, you can use CocoaPods on macOS to automatically install the swiftformat binary along with your other pods - see the Xcode build phase instructions below for details.

Another option is to include the binary artifactbundle in your Package.swift:

.binaryTarget(
    name: "swiftformat",
    url: "https://github.com/nicklockwood/SwiftFormat/releases/download/0.55.0/swiftformat-macos.artifactbundle.zip",
    checksum: "CHECKSUM"
),

If you would prefer not to use a package manager, you can build the command-line app manually:

1. open SwiftFormat.xcodeproj and build the SwiftFormat (Application) scheme.

2. Drag the swiftformat binary into /usr/local/bin/ (this is a hidden folder, but you can use the Finder's Go > Go to Folder... menu to open it).

3. Open ~/.bash_profile in your favorite text editor (this is a hidden file, but you can type open ~/.bash_profile in the terminal to open it).

4. Add the following line to the file: alias swiftformat="/usr/local/bin/swiftformat --indent 4" (you can omit the --indent 4, or replace it with something else. Run swiftformat --help to see the available options).

5. Save the .bash_profile file and run the command source ~/.bash_profile for the changes to take effect.

Usage:

If you followed the installation instructions above, you can now just type

$ swiftformat .

(that's a space and then a period after the command) in the terminal to format any Swift files in the current directory. In place of the ., you can instead type an absolute or relative path to the file or directory that you want to format.

WARNING: swiftformat . will overwrite any Swift files it finds in the current directory, and any subfolders therein. If you run it in your home directory, it will probably reformat every Swift file on your hard drive.

To use it safely, do the following:

1. Choose a file or directory that you want to apply the changes to.

2. Make sure that you have committed all your changes to that code safely in git (or whatever source control system you use).

3. (Optional) In Terminal, type swiftformat --infer-options "/path/to/your/code/". This will suggest a set of formatting options to use that match your existing project style (but you are free to ignore these and use the defaults, or your own settings if you prefer).

The path can point to either a single Swift file or a directory of files. It can be either be absolute, or relative to the current directory. The "" quotes around the path are optional, but if the path contains spaces then you either need to use quotes, or escape each space with \. You may include multiple paths separated by spaces.

4. In Terminal, type swiftformat "/path/to/your/code/". The same rules apply as above with respect to paths, and multiple space-delimited paths are allowed.

If you used --infer-options to generate a suggested set of options in step 3, you should copy and paste them into the command, either before or after the path(s) to your source files.

If you have created a config file, you can specify its path using --config "/path/to/your/config-file/". Alternatively, if you name the file .swiftformat and place it inside the project you are formatting, it will be picked up automatically.

5. Press enter to begin formatting. Once the formatting is complete, use your source control system to check the changes, and verify that no undesirable changes have been introduced. If they have, revert the changes, tweak the options and try again.

6. (Optional) commit the changes.

Following these instructions should ensure that you avoid catastrophic data loss, but in the unlikely event that it wipes your hard drive, please note that I accept no responsibility.

Using Standard Input/Output:

If you prefer, you can use unix pipes to include SwiftFormat as part of a command chain. For example, this is an alternative way to format a file:

$ cat /path/to/file.swift | swiftformat --output /path/to/file.swift

Omitting the --output /path/to/file.swift will print the formatted file to Standard Output (stdout). You can also pass "stdout" explicitly as the output path:

$ cat /path/to/file.swift | swiftformat --output stdout

Or you can use > to specify the output path as follows:

$ cat /path/to/file.swift | swiftformat > /path/to/file.swift

If you do not supply an input file, SwiftFormat will automatically take its input from Standard Input (stdin), but will time-out if no input is received immediately and display the help screen. To make it explicit, pass "stdin" as the input path:

$ cat /path/to/file.swift | swiftformat stdin

When using stdin, SwiftFormat does not have access to the file path of the input, so features that rely on the file location (such as inserting the creation date into header comments, or detecting .swiftformat configuration files in the file path) will not work. To solve this, you can provide the file path using the --stdin-path argument:

$ cat /path/to/file.swift | swiftformat stdin --stdinpath /path/to/file.swift

Xcode source editor extension
-----------------------------

Installation:

Like the command-line tool, you can install the SwiftFormat for Xcode extension application via Homebrew. Assuming you already have Homebrew installed, type:

$ brew install --cask swiftformat-for-xcode

This will install SwiftFormat for Xcode in your Applications folder. Double-click the app to launch it, and then follow the on-screen instructions.

NOTE: The app should be correctly signed, but if you get a Gatekeeper warning when trying to open it you can bypass this by right-clicking (or control-clicking) the app and selecting Open.

To update to the latest version once installed use:

$ brew upgrade --cask swiftformat-for-xcode

Alternatively, if you prefer not to use Homebrew, you'll find the latest version of the SwiftFormat for Xcode application on the GitHub Releases page. Download and unpack the zip archive, then drag SwiftFormat for Xcode.app into your Applications folder.

Usage:

Once you have launched the app and restarted Xcode, you'll find a SwiftFormat option under Xcode's Editor menu. If the SwiftFormat menu does not appear this thread may help.

You can configure the formatting rules and options using the SwiftFormat for Xcode host application. There is currently no way to override these per-project, however, you can import and export different configurations using the File menu. You will need to do this again each time you switch projects.

The format of the configuration file is described in the Config section below.

Note: SwiftFormat for Xcode cannot automatically detect changes to an imported configuration file. If you update the .swiftformat file for your project, you will need to manually re-import that file into SwiftFormat for Xcode in order for the Xcode source editor extension to use the new configuration.

Xcode build phase
-------------------

NOTE: Adding this script will overwrite your source files as you work on them, which has the annoying side-effect of clearing the undo history. You may wish to add the script to your test target rather than your main target, so that it is invoked only when you run the unit tests, and not every time you build the app.

Alternatively, you might want to consider running SwiftFormat in lint mode as part of your normal build, and then running a formatting pass manually, or as part of a less-frequent build target (such as the tests).

Using Swift Package Manager Copy Section

To set up SwiftFormat as an Xcode build phase, do the following:

#### 1) Create a BuildTools folder and Package.swift

1. Create a folder called BuildTools in the same folder as your xcodeproj file
2. In this folder, create a file called Package.swift, with the following contents:

// swift-tools-version:5.1
import PackageDescription
let package = Package(
    name: "BuildTools",
    platforms: [.macOS(.v10_11)],
    dependencies: [
        .package(url: "https://github.com/nicklockwood/SwiftFormat", from: "0.61.0"),
    ],
    targets: [.target(name: "BuildTools", path: "")]
)

#### 2) Add a Build phase to your app target

1. Click on your project in the file list, choose your target under TARGETS, click the Build Phases tab
2. Add a New Run Script Phase by clicking the little plus icon in the top left
3. Uncheck the Based on dependency analysis checkbox
4. Drag the new Run Script phase above the Compile Sources phase, expand it and paste the following script:

cd BuildTools
    SDKROOT=(xcrun --sdk macosx --show-sdk-path)
    #swift package update #Uncomment this line temporarily to update the version used to the latest matching your BuildTools/Package.swift file
    swift run -c release swiftformat "$SRCROOT"

You can also use swift run -c release --package-path BuildTools swiftformat "$SRCROOT" if you need a more complex script and cd BuildTools breaks stuff.

NOTE: You may wish to check BuildTools/Package.swift into your source control so that the version used by your run-script phase is kept in version control. It is recommended to add the following to your .gitignore file: BuildTools/.build and BuildTools/.swiftpm.

NOTE (2): If you are using Xcode 15 or later, make sure that the ENABLE_USER_SCRIPT_SANDBOXING (aka "User Script Sandboxing") option is set to NO, otherwise SwiftFormat won't be able to run correctly.

Using CocoaPods Copy Section

#### 1) Add the SwiftFormat CLI to your Podfile

1. Add the swiftformat binary to your project directory via CocoaPods, by adding the following line to your Podfile then running pod install:

pod 'SwiftFormat/CLI', '~> 0.61.0'

NOTE: This will only install the pre-built command-line app, not the source code for the SwiftFormat framework.

NOTE (2): When installing this way, GateKeeper may block swiftformat from running until you open it manually the first time by right-clicking in the Finder and selecting "Open".

#### 2) Add a Build phase to your app target

1. Click on your project in the file list, choose your target under TARGETS, click the Build Phases tab
2. Add a New Run Script Phase by clicking the little plus icon in the top left
3. Uncheck the Based on dependency analysis checkbox
4. Drag the new Run Script phase above the Compile Sources phase, expand it and paste the following script:

"${PODS_ROOT}/SwiftFormat/CommandLineTool/swiftformat" "$SRCROOT"

Alternative: Locally installed SwiftFormat Copy Section

Alternatively, you could use a locally installed swiftformat command-line tool instead by putting the following in your Run Script build phase:

if which swiftformat >/dev/null; then
  swiftformat .
else
  echo "warning: SwiftFormat not installed, download from https://github.com/nicklockwood/SwiftFormat"
fi

This is not recommended for shared projects however, as different team members using different versions of SwiftFormat may result in noise in the commit history as code gets reformatted inconsistently.

If you installed SwiftFormat via Homebrew on Apple Silicon, you might experience this warning:

warning: SwiftFormat not installed, download from https://github.com/nicklockwood/SwiftFormat

That is because Homebrew on Apple Silicon installs the binaries into the /opt/homebrew/bin
folder by default. To instruct Xcode where to find SwiftFormat, you can either add
/opt/homebrew/bin to the PATH environment variable in your build phase

if [[ "$(uname -m)" == arm64 ]]; then
    export PATH="/opt/homebrew/bin:$PATH"
fi
if which swiftformat > /dev/null; then
  swiftformat .
else
  echo "warning: SwiftFormat not installed, download from https://github.com/nicklockwood/SwiftFormat"
fi

or you can create a symbolic link in /usr/local/bin pointing to the actual binary:

ln -s /opt/homebrew/bin/swiftformat /usr/local/bin/swiftformat

Swift Package Manager plugin
-----------------------------

You can use SwiftFormat as a SwiftPM command plugin.

NOTE: Swift 5.6 or higher is required. Add the package to your dependencies in your Package.swift file.

dependencies: [
    // ...
    .package(url: "https://github.com/nicklockwood/SwiftFormat", from: "0.61.0"),
]

The plugin will find an existing .swiftformat in your package root folder and honor it automatically.

Trigger Plugin From Command-Line Copy Section

swift package plugin --allow-writing-to-package-directory swiftformat

You can limit the formatting to a particular target with --target option.

You can also specify SwiftFormat arguments, e.g. --swift-version.

Example

swift package plugin --allow-writing-to-package-directory swiftformat --target MyLibrary --swift-version 5.6 --verbose

Trigger Plugin From Xcode Copy Section

In Xcode 14 you can trigger the command plugin execution for a Swift package or an Xcode project.

For an Xcode project the project's main directory will be processed and the --target option will be ignored.

You can also specify SwiftFormat arguments, e.g. --swift-version.

!Run plugin in Xcode 14

Via AppleScript
----------------

To run SwiftFormat on the frontmost Xcode document (project or workspace) you can use the following AppleScript:

tell application "Xcode"
    set frontWindow to the first window
    set myPath to path of document of frontWindow
    do shell script "cd " & myPath & ";cd ..; /usr/local/bin/swiftformat ."
end tell

Some Apps you can trigger this from are BetterTouchTool, Alfred or Keyboard Maestro. Another option is to define a QuickAction for Xcode via Automator and then assign a keyboard shortcut for it in the System Preferences.

VSCode plugin
--------------

If you prefer to use Microsoft's VSCode editor for writing Swift, Valentin Knabel has created a VSCode plugin for SwiftFormat.

Sublime Text plugin
--------------------

If you prefer to use the Sublime Text editor, try the Sublime-Swift-Format plugin by Aerobounce.

Nova plugin
-----------

If you prefer to use the Nova editor, try the SwiftFormat extension by Pádraig Ó Cinnéide.

Git pre-commit hook
---------------------

1. Follow the instructions for installing the SwiftFormat command-line tool.

2. Install git-format-staged.

3. Edit or create a .git/hooks/pre-commit file in your project folder. The .git folder is hidden but should already exist if you are using Git with your project, so open it with the terminal, or the Finder's Go > Go to Folder... menu.

4. Add the following line in the pre-commit file. The {} will be replaced automatically by the path to the Swift file being formatted:

#!/bin/bash
    git-format-staged --formatter "swiftformat stdin --stdin-path '{}'" "*.swift"

NOTE: If you are using Git via a GUI client such as Tower, additional steps may be needed.

NOTE (2): Unlike the Xcode build phase approach, git pre-commit hook won't be checked in to source control, and there's no way to guarantee that all users of the project are using the same version of SwiftFormat. For a collaborative project, you might want to consider a post-commit hook instead, which would run on your continuous integration server.

GitHub Actions
---------------------

1. SwiftFormat comes preinstalled on all macOS GitHub-hosted runners. If you are self hosting you will need to ensure SwiftFormat is installed on your runner.
2. Create a GitHub Actions workflow using SwiftFormat, passing the --reporter github-actions-log command line option. The following example action lints pull requests using SwiftFormat, reporting warnings using the GitHub Actions log.

Lint.yml

name: Lint
on: pull_request
jobs:
  Lint:
    runs-on: macos-latest
    steps:
      - uses: actions/checkout@v4
      - name: SwiftFormat
        run: swiftformat --lint . --reporter github-actions-log

On CI using Danger
-------------------

To setup SwiftFormat to be used by your continuous integration system using Danger, do the following:

1. Follow the instructions to setup Danger.
2. Add the danger-swiftformat plugin to your Gemfile.
3. Add the following to your Dangerfile:

swiftformat.binary_path = "/path/to/swiftformat" # optional
    swiftformat.additional_args = "--indent tab --self insert" # optional
    swiftformat.check_format(fail_on_error: true)

NOTE: It is recommended to add the swiftformat binary to your project directory to ensure the same version is used each time (see the Xcode build phase instructions above).

Bazel Build
-----------

If you use Bazel to build your Swift projects and want to ensure that only properly formatted code is merged to your main branch, try rules_swiftformat. The repository contains Bazel rules and macros that format Swift source files using SwiftFormat, test that the formatted files exist in the workspace directory, and copy the formatted files to the workspace directory.

Docker
-----------

SwiftFormat publishes releases into GitHub Packages Docker registry. To pull the image call:

$ docker pull ghcr.io/nicklockwood/swiftformat:latest

By default, the container runs swiftformat . Therefore, you need to provide a path either via an argument:

docker run --rm -v /local/source/path:/work ghcr.io/nicklockwood/swiftformat:latest /work

or by changing the working dir:

docker run --rm -v /local/source/path:/work -w /work ghcr.io/nicklockwood/swiftformat:latest

To check the installed SwiftFormat version:

docker run --rm ghcr.io/nicklockwood/swiftformat:latest --version

Linting example:

docker run --rm -v /local/source/path:/work ghcr.io/nicklockwood/swiftformat:latest /work --lint

Prerelease Builds
-----------------

Prerelease builds are subject to breaking changes.

New rules, options, and fixes are merged to the develop branch before being incorporated into an official release. You may want to use a prerelease version of SwiftFormat that includes the latest unreleased changes.

Homebrew:

The Homebrew --HEAD option downloads, builds, and installs the latest changes from the develop branch.

You can install a prerelease build via Homebrew by running:

$ brew install swiftformat --HEAD

Nightly Builds:

Nightly builds of the develop branch are available in the calda/SwiftFormat-nightly repo. A new release is published every day, unless there have been no changes to develop since the last release. You can download executables for the latest nightly release here.

Commit SHAs on develop are unstable since that branch is occasionally rebased, but artifact URLs and tags in calda/SwiftFormat-nightly are stable references that can be used from other repos or tools.

Configuration
-------------

SwiftFormat's configuration is split between rules and options. Rules are functions in the SwiftFormat library that apply changes to the code. Options are settings that control the behavior of the rules.

Options
-------

The options available in SwiftFormat can be displayed using the --options command-line argument. The default value for each option is indicated in the help text.

Rules are configured by adding --[option_name] [value] to your command-line arguments, or by creating a .swiftformat config file and placing it in your project directory.

A given option may affect multiple rules. Use --rule-info [rule_name] command for details about which options affect a given rule, or see the Rules.md file.

You can configure options for specific files or code ranges by using swiftformat:options directive in comments inside your Swift file. To temporarily set one or more options inside a source file, use:

// swiftformat:options --indent 2 --allman true

To apply an options override only to a particular line, use the :this, :next or :previous modifiers:

let indexUrl: URL // swiftformat:options:this --preserve-acronyms url 
// swiftformat:options:next --semicolons inline
doTheThing(); print("Did the thing")

Rules
-----

SwiftFormat includes over 50 rules, and new ones are added all the time. An up-to-date list can be found in Rules.md along with documentation for how they are used.

The list of available rules can be displayed within the command-line app using the --rules argument. Rules can be either enabled or disabled. Most are enabled by default. Disabled rules are marked with "(disabled)" when displayed using --rules.

You can use the --rule-info [rule_name] command to get information about a specific rule. Pass a comma-delimited list of rule names to get information for multiple rules at once, or use --rule-info with no argument for info on all rules.

You can disable rules individually using --disable followed by a list of one or more comma-delimited rule names, or enable opt-in rules using --enable followed by the rule names:

--disable redundantSelf,trailingClosures
--enable isEmpty

If you prefer, you can use multiple --enable/--disable arguments instead of using commas:

--disable indent
--disable linebreaks
--disable redundantSelf

Alternatively, you can use the line continuation character \ to wrap a single argument over multiple line:

``bash
--disable \
indent, \
linebreaks, \
redundantSelf


To avoid automatically opting-in to new rules when SwiftFormat is updated, you can disable all rules using:

And then individually enable just the rules you want. Alternatively, use the--rules argument to only enable the rules you specify:

As above, you may include multiple --rules arguments, or use the line continuation character \ to wrap the rules onto separate lines:

To see exactly which rules were applied to a given file, you can use the --verbose command-line option to force SwiftFormat to print a more detailed log as it applies the formatting. NOTE: running in verbose mode is slower than the default mode.
You can disable rules for specific files or code ranges by using swiftformat: directives in comments inside your Swift file. To temporarily disable one or more rules inside a source file, use:

To enable the rule(s) again, use:

To disable all rules use:

And to enable them all again, use:

To temporarily prevent one or more rules being applied to just the next line, use:

You can also use this or previous to enable or disable rules for the current or previous line. There is no need to manually re-enable a rule after using the next, this or previous directives.
NOTE: The swiftformat:enable directive only serves to counter a previous swiftformat:disable directive in the same file. It is not possible to use swiftformat:enable to enable a rule that was not already enabled when formatting started.

Swift version
-------------
Most SwiftFormat rules are version-agnostic, but some are applicable only to newer Swift versions. These rules will be disabled automatically if the Swift version is not specified, so to make sure that the full functionality is available you should specify the version of Swift that is used by your project.
You can specify the Swift compiler version in one of two ways:
You can specify your project's Swift compiler version using the --swift-version command line argument. You can also add the --swift-version option to your .swiftformat file.
Another option is to add a .swift-version file to your project directory. This is a text file that should contain the minimum Swift version supported by your project, and is also supported by some other tools. Any .swift-version files always take precedence over the --swift-version argument.
Both the .swift-version file and the --swift-version option in a .swiftformat file are applied hierarchically; If you have submodules in your project that use a different Swift version, you can add separate swift version configurations for those directories.
Swift language mode
-------------------
SwiftFormat also allows you to specify the Swift _language mode_ used by your project. This is distinct from the Swift compiler version. For example, you can use the Swift 6.0 compiler with either the Swift 5 language mode or the Swift 6 language mode. Some SwiftFormat rules will behave differently under different Swift language modes.
You can specify your project's Swift language mode using the --language-mode command line argument. You can also add the --language-mode option to your .swiftformat file.
If not specified, SwiftFormat uses the default language mode of the specified Swift compiler version. The default language mode in Swift 5.x and Swift 6.x is the Swift 5 language mode. If your project uses the Swift 6 language mode, you should specify --language-mode 6.

Config file
-----------
Although it is possible to configure SwiftFormat directly by using the command-line options and rules detailed above, it is sometimes more convenient to create a configuration file, which can be added to your project and shared with other developers.
A SwiftFormat configuration file consists of one or more command-line options, split onto separate lines, e.g:

While formatting, SwiftFormat will automatically check inside each subdirectory for the presence of a .swiftformat file and will apply any options that it finds there to the files in that directory.
This allows you to override certain rules or formatting options just for a particular directory of files. You can also specify excluded files relative to that directory using --exclude, which may be more convenient than specifying them at the top-level:

The --exclude option takes a comma-delimited list of file or directory paths to exclude from formatting. Excluded paths are relative to the config file containing the --exclude command. The excluded paths can include wildcards, specified using Unix "Glob" syntax, as documented below.
Config files named ".swiftformat" will be processed automatically, however, you can select an additional configuration file to use for formatting using the --config "path/to/config/file" command-line argument. A configuration file selected using --config does not need to be named ".swiftformat", and can be located outside of the project directory.
The config file format is designed to be edited by hand. You may include blank lines for readability, and can also add comments using a hash prefix (#), e.g.

You can create multiple configuration sections within a single .swiftformat file to apply different formatting options to different parts of your project. Each section should specify a --filter glob pattern to determine which files the configuration applies to. Options in that section are used when formatting files that match --filter glob, in addition to the base options in the file.

If you would prefer not to edit the configuration file by hand, you can use the SwiftFormat for Xcode app to edit the configuration and export a configuration file. You can also use the swiftformat command-line-tool's --infer-options command to generate a config file from your existing project, like this:

Globs
-----
When excluding files from formatting using the --exclude option, you may wish to make use of wildcard paths (aka "Globs") to match all files that match a particular naming convention without having to manually list them all.
SwiftFormat's glob syntax is based on Ruby's implementation, which varies slightly from the Unix standard. The following patterns are supported:
  - A single star matches zero or more characters in a filename, but not a /.
 * - A double star will match anything, including one or more /.
* ? - A question mark will match any single character except /.
* [abc] - Matches any single character inside the brackets.
* [a-z] - Matches a single character in the specified range in the brackets.
* {foo,bar} - Matches any one of the comma-delimited strings inside the braces.
Examples:
* foo.swift - Matches the file "foo.swift" in the same directory as the config file.
 .swift - Matches any Swift file in the same directory as the config file.
* foo/bar.swift - Matches the file "bar.swift" in the directory "foo".
 */foo.swift - Matches any file named "foo.swift" in the project.
 /.swift - Matches any Swift file in the project.
 */Generated - Matches any folder called Generated in the project.
 /_generated.swift - Matches any Swift file with the suffix "_generated" in the project.

Linting
-------
SwiftFormat is primarily designed as a formatter rather than a linter, i.e. it is designed to fix your code rather than tell you what's wrong with it. However, sometimes it can be useful to verify that code has been formatted in a context where it is not desirable to actually change it.
A typical example would be as part of a CI (Continuous Integration) process, where you may wish to have an automated script that checks committed code for style violations. While you can use a separate tool such as SwiftLint for this, it makes sense to be able to validate the formatting against the exact same rules as you are using to apply it.
In order to run SwiftFormat as a linter, you can use the --lint command-line option:

This runs the same rules as format mode, and all the same configuration options apply, however, no files will be modified. Instead, SwiftFormat will format each file in memory and then compare the result against the input and report the lines that required changes.
The --lint option is similar to --dry-run, but --lint returns warnings for every line that required changes, and will return a nonzero error code (see Error codes below) if any changes are detected, which is useful if you want it to fail a build step on your CI server.
If you would prefer --lint not to fail your build, you can use the --lenient option to force SwiftFormat to return success in --lint mode even when formatting issues were detected.

By default, --lint will only report lines that require formatting, but you can use the additional --verbose flag to display additional info about which files were checked, even if there were no changes needed.
If you would prefer not to see a warning for each and every formatting change, you can use the --quiet flag to suppress all output except errors.
Sometimes you may wish to autoformat some rules, but only lint others. To do that, use the --lintonly option in your config file to specify rules that should only be applied in --lint mode:

Error codes
-----------
The swiftformat command-line tool will always exit with one of the following codes:
* 0 - Success. This code will be returned in the event of a successful formatting run or if --lint detects no violations.
* 1 - Lint failure. This code will be returned when running in --lint mode, or when autocorrecting in --strict mode, if the input requires formatting.
* 70 - Program error. This code will be returned if there is a problem with the input or configuration arguments.

Cache
------
SwiftFormat uses a cache file to avoid reformatting files that haven't changed. For a large project, this can significantly reduce processing time.
By default, the cache is stored in ~/Library/Caches/com.charcoaldesign.swiftformat on macOS, or /tmp/com.charcoaldesign.swiftformat on Linux. Use the command-line option --cache ignore to ignore the cached version and re-apply formatting to all files. Alternatively, you can use --cache clear to delete the cache (or you can just manually delete the cache file).
The cache is shared between all projects. The file is fairly small, as it only stores the path and size for each file, not the contents. If you do start experiencing slowdown due to the cache growing too large, you might want to consider using a separate cache file for each project.
You can specify a custom cache file location by passing a path as the --cache option value. For example, you might want to store the cache file inside your project directory. It is fine to check in the cache file if you want to share it between different users of your project, as the paths stored in the cache are relative to the location of the formatted files.

File headers
-------------
SwiftFormat can be configured to strip or replace the header comments in every file with a template. The "header comment" is defined as a comment block that begins on the first nonblank line in the file, and is followed by at least one blank line. This may consist of a single comment body, or multiple comments on consecutive lines:

The header template is a string that you provide using the --header command-line option. Passing a value of ignore (the default) will leave the header comments unmodified. Passing strip or an empty string "" will remove them. If you wish to provide a custom header template, the format is as follows:
For a single-line template: --header "Copyright (c) 2017 Foobar Industries"
For a multiline comment, mark linebreaks with \n: --header "First line\nSecond line"
You can optionally include Swift comment markup in the template if you wish: --header "/--- Header comment ---/"
If you do not include comment markup, each line in the template will be prepended with // and a single space.
It is common practice to include the file name, creation date and/or the current year in a comment header copyright notice. To do that, you can use the following placeholders:
* {file} - the name of the file
* {year} - the current year
* {created} - the date on which the file was created
* {created.year} - the year in which the file was created
* {author.name} - the name of the user who first committed the file
* {author.email} - the email of the user who first committed the file 
For example, a header template of:

Will be formatted as:

NOTE: the {year} value and {created} date format are determined from the current locale and timezone of the machine running the script. {author.name} and {author.email} requires the project to be version controlled by git.

Markdown formatting
-------------------
SwiftFormat can format Swift code blocks inside Markdown files (.md). This is useful for keeping code examples in documentation, README files, and other markdown content properly formatted.

func foo(
- bar: Bar,
- baaz: Baaz
+     bar: Bar,
+     baaz: Baaz
  ) -> Foo { ... }

To format Swift code blocks in markdown files, use the --markdown-files option with either strict or lenient:

Or add it to your .swiftformat config file:

Formatting modes:
SwiftFormat supports two modes for handling markdown files:
- lenient (default): Ignores parsing errors in code blocks and continues formatting
- strict: Fails if any code blocks contain parsing errors
SwiftFormat's tokenizer is more permissive than the Swift compiler and typically only emits errors when encountering unbalanced scope tokens like ( or {.
Code block options:
You can specify options for options for individual code blocks by adding them after the opening delimiter. For example, you can use no-format to prevent a code block from being parsed or formatted:

You can also specify SwiftFormat command line options to configure the behavior of individual rules:

FAQ
-----

Q. How is this different from SwiftLint?

A. SwiftLint is primarily designed to find and report code smells and style violations in your code. SwiftFormat is designed to fix them. While SwiftLint can autocorrect some issues, and SwiftFormat has some support for linting, their primary functions are different.

Q. Can SwiftFormat and SwiftLint be used together?

A. Absolutely! The style rules encouraged by both tools are quite similar, and SwiftFormat even fixes some style violations that SwiftLint warns about but can't currently autocorrect.

Q. What platforms does SwiftFormat support?

A. SwiftFormat works on macOS 10.13 (High Sierra) and above, and also runs on Ubuntu Linux and Windows.

Q. What versions of Swift are supported?

A. The SwiftFormat framework and command-line tool can be compiled using Swift 5.3 and above, and can format programs written in Swift 4.x or 5. Swift 3.x is no longer actively supported. If you are still using Swift 3.x or earlier and find that SwiftFormat breaks your code, the best solution is probably to revert to an earlier SwiftFormat release, or enable only a small subset of rules. Use the --swift-version argument to enable additional rules specific to later Swift versions.

Q. SwiftFormat made changes I didn't want it to. How can I find out which rules to disable?

A. If you run SwiftFormat using the --verbose option, it will tell you which rules were applied to each file. You can then selectively disable certain rules using the --disable argument (see below).

*Q. People on my team have different SwiftFormat versions installed. How can we ensure consistent formatting?

A. You can specify a --min-version argument in your project's .swiftformat file to fail the build if developers attempt to use an older SwiftFormat version.


Q. How can I modify the formatting rules?

A. Many configuration options are exposed in the command-line interface or .swiftformat configuration file. You can either set these manually, or use the --infer-options argument to automatically generate the configuration from your existing project.

If there is a rule that you don't like, and which cannot be configured to your liking via the command-line options, you can disable one or more rules by using the --disable argument, followed by the name of the rules, separated by commas. You can display a list of all supported rules using the --rules argument, and their behaviors are documented above this section in the README.

If you are using the Xcode source editor extension, rules and options can be configured using the SwiftFormat for Xcode host application. Unfortunately, due to limitation of the Extensions API, there is no way to configure these on a per-project basis.

If the options you want aren't exposed, and disabling the rule doesn't solve the problem, the rules are implemented in the file Rules.swift, so you can modify them and build a new version of the command-line tool. If you think your changes might be generally useful, make a pull request.


Q. I don't want to be surprised by new rules added when I upgrade SwiftFormat. How can I prevent this?

A. You can use the --rules argument to specify an exclusive list of rules to run. If new rules are added, they won't be enabled if you have specified a --rules list in your SwiftFormat configuration.


Q. Why can't I set the indent width or choose between tabs/spaces in the SwiftFormat for Xcode options?

Indent width and tabs/spaces can be configured in Xcode on a per project-basis. You'll find the option under "Text Settings" in the Files inspector of the right-hand sidebar.


Q. After applying SwiftFormat, my code won't compile. Is that a bug?

A. SwiftFormat should ideally never break your code. Check the known issues, and if it's not already listed there, or the suggested workaround doesn't solve your problem, please open an issue on GitHub.


Q. Can I use SwiftFormat to lint my code without changing it?

A. Yes, see the linting section above for details.


Q. Can I use the SwiftFormat.framework inside another app?

A. Yes, the SwiftFormat framework can be included in an app or test target, and used for many kinds of parsing and processing of Swift source code besides formatting. The SwiftFormat framework is available as a CocoaPod for easy integration.

Q. How to create own rule?

A. 1) Open SwiftFormat.xcodeproj; 2) Add a rule in Sources/Rules/..; 3) Add a test in Tests/Rules/..; 4) Add an example in Sources/Examples.swift; 5) Run all tests.

Q. How do I run and debug the command line tool in Xcode while developing a new rule?

A. You can run the swiftformat command line tool via the Swift Format (Command Line Tool) scheme, and you can pass in arguments like /path/to/my/code --config /path/to/my/config as the Arguments Passed On Launch in Xcode's scheme editor. More instructions are available here.

Known issues
---------------

* When using the Xcode Source Editor Extension, the SwiftFormat menu sometimes disappears from Xcode. If this happens, try moving or renaming Xcode temporarily and then changing it back. Failing that, the suggestions in this thread may help.

* The enumNamespaces rule replaces classes that have only static members with an enum. If the class is subclassed, or if there is code that depends on the class exposing certain runtime behaviors, this may break the program. To solve this you can either fix it on a per-case basis by adding a // swiftformat:disable:next enumNamespaces comment directive above the class declaration, or you can add --enum-namespaces structs-only to prevent the rule being applied to classes, or you can just disable the enumNamespaces rule completely.

* The redundantVoidReturnType rule can inadvertently alter the type signature for closures, for example in cases where the closure calls a @discardableResult function. To solve this you can either fix it on a per-case basis by adding a // swiftformat:disable:next redundantVoidReturnType comment directive to disable the rule for a specific call site, or you can add --closure-void preserve to your configuration to disable the rule completely for closures (regular functions or methods aren't affected).

* The redundantType rule can introduce ambiguous code in certain cases when using the default mode of --redundant-type inferred. This can be worked around by by using --redundant-type explicit, or by manually removing the redundant type reference on the affected line, or by using the // swiftformat:disable:next redundantType comment directive to disable the rule at the call site (or just disable the redundantType rule completely).

* If a type initializer or factory method returns an implicitly unwrapped optional value then the redundantType rule may remove the explicit type in a situation where it's actually required. To work around this you can either use --redundant-type explicit, or use the // swiftformat:disable:next redundantType comment directive to disable the rule at the call site (or just disable the redundantType rule completely).

* When using the initCoderUnavailable rule, if an init that is marked as unavailable is overridden elsewhere in the program then it will cause a compilation error. The recommended workaround is to remove the override (which shouldn't affect the program behavior if the init was really unused) or use the // swiftformat:disable:next initCoderUnavailable comment directive to disable the rule for the overridden init (or just disable the initCoderUnavailable rule completely).

* When using the extensionAccessControl rule with the --extension-acl on-extension option, if you have public methods defined on an internal type defined in another file, the resultant public extension will no longer compile. The recommended solution is to manually remove the public modifier (this won't change the program behavior) or disable the extensionAccessControl rule.

* When using the preferKeyPath rule, conversion of compactMap { $0.foo } to compactMap(\.foo) or flatMap { $0.foo } to flatMap(\.foo) will result in code that fails to compile if foo is not an Optional property. This is due to a difference in the way that Swift handles type inference for closures vs keyPaths, as discussed here. The recommended workaround is to replace compactMap() or flatMap() with map() in these cases, which will not change the behavior of the code.

* When using the --self remove option, the redundantSelf rule will remove references to self in autoclosure arguments, which may change the meaning of the code, or cause it not to compile. To work around this issue, use the --self-required option to provide a comma-delimited list of methods to be excluded from the rule. The expect() function from the popular Nimble unit testing framework is already excluded by default. If you are using the --self insert option then this is not an issue.

* If you assign SomeClass.self to a variable and then instantiate an instance of the class using that variable, Swift requires that you use an explicit .init(), however, the redundantInit rule is not currently capable of detecting this situation in all cases, and may remove the .init. To work around this issue, use the // swiftformat:disable:next redundantInit comment directive to disable the rule for any affected lines of code (or just disable the redundantInit rule completely).

The --self insert option can only recognize locally declared member variables, not ones inherited from superclasses or extensions in other files, so it cannot insert missing self references for those. Note that the reverse is not true: --self remove should remove all* redundant self references.

* The trailingClosures rule can generate ambiguous code if a function has multiple optional closure arguments, or if multiple functions have signatures differing only by the name of the closure argument. For this reason, the rule is limited to anonymous closure arguments by default. You can use the --trailing-closures and --never-trailing arguments to explicitly opt in or out of trailing closure support for specific functions.

* The isEmpty rule will convert count == 0 to isEmpty even for types that do not have an isEmpty method, such as NSArray/NSDictionary/etc. Use of Foundation collections in Swift code is pretty rare, but just in case, the rule is disabled by default.

* The preferForLoop rule will convert foo.forEach to for item in foo even for types that do not conform to the Sequence protocol and cannot be used with a for ... in loop. There are no such types built in, but custom types may have this issue.

* If a file begins with a comment, the stripHeaders rule will remove it if it is followed by a blank line. To avoid this, make sure that the first comment is directly followed by a line of code.

* When running a version of SwiftFormat built using Xcode 10.2 on macOS 10.14.3 or earlier, you may experience a crash with the error "dyld: Library not loaded: @rpath/libswiftCore.dylib". To fix this, you need to install the Swift 5 Runtime Support for Command Line Tools. These tools are included by default in macOS 10.14.4 and later.

* If you have a generic typealias that defines a closure (e.g. typealias ResultCompletion<T> = (Result<T, Error>) -> Void) and use this closure as an argument in a generic function (e.g. func handle<T: Decodable>(_ completion: ResultCompletion<T>)), the opaqueGenericParameters rule may update the function definition to use some syntax (e.g. func handle(_ completion: ResultCompletion<some Decodable>)). some syntax is not permitted in closure parameters, so this will no longer compile. Workarounds include spelling out the closure explicitly in the generic function (instead of using a typealias) or disabling the opaqueGenericParameters rule (e.g. with // swiftformat:disable:next opaqueGenericParameters).

* If compiling for macOS with Xcode 14.0 and configuring SwiftFormat with --swift-version 5.7, the genericExtensions rule may cause a build failure by updating extensions of the format extension Collection where Element == Foo to extension Collection<Foo>. This fails to compile for macOS in Xcode 14.0, because the macOS SDK in that version of Xcode does not include the Swift 5.7 standard library. Workarounds include using --swift-version 5.6 instead, updating to Xcode 14.1+, or disabling the genericExtensions rule (e.g. with // swiftformat:disable:next genericExtensions).

* The propertyTypes rule can cause a build failure in cases where there are multiple static overloads with the same name but different return types. As a workaround you can rename the overloads to no longer conflict, or exclude the property name with --preserve-symbols propertyName,otherPropertyName,etc.

* The propertyTypes rule can cause a build failure in cases where the property's type is a protocol / existential like let shapeStyle: ShapeStyle = .myShapeStyle, and the value used on the right-hand side is defined in an extension like extension ShapeStyle where Self == MyShapeStyle { static var myShapeStyle: MyShapeStyle { ... } }. As a workaround you can use the existential any syntax (let shapeStyle: any ShapeStyle = .myShapeStyle), which the rule will preserve as-is, or exclude the type name and/or property name with --preserve-symbols ShapeStyle,myShapeStyle,etc.

* The propertyTypes rule can cause a build failure in cases like let foo = Foo.bar where the value is a static member that doesn't return the same time. For example, let foo: Foo = .bar would be invalid if the bar property was defined as static var bar: Bar. As a workaround you can write the name of the type explicitly, like let foo: Bar = Foo.bar, or exclude the type name and/or property name with --preserve-symbols Bar,bar,etc.

* The propertyTypes rule can cause a build failure in cases like let value = Tools.makeString() where Tools is used as a namespace (e.g. a caseless enum) and makeString() is a static factory method that returns a different type (e.g. String). The rule converts this to let value: Tools = .makeString(), which fails to compile. As a workaround you can write the type explicitly, like let value: String = Tools.makeString(), or exclude the type name and/or property name with --preserve-symbols Tools,makeString,etc, or use // swiftformat:disable:next propertyTypes.

* The redundantEquatable rule may incorrectly remove a == implementation that intentionally overrides a default == provided by another protocol. For example, Strideable provides a default == implementation derived from distance(to:), and a type may override it with a custom ==. SwiftFormat handles this case when the Strideable conformance is defined in the same file, but it cannot detect conformances in a different file, nor default == implementations provided by other protocols. As a workaround you can use the // swiftformat:disable:next redundantEquatable comment directive to disable the rule for the affected type (or just disable the redundantEquatable` rule completely).

Tip Jar
-----------

SwiftFormat is not a commercially-funded product, it's a labor of love given freely to the community. If you find it useful, please consider making a donation.


Credits
------------

* Cal Stephens - Numerous new formatting rules, options and bug fixes
* Tony Arnold - SwiftFormat for Xcode
* Vincent Bernier - SwiftFormat for Xcode settings UI
* Vikram Kriplaney - SwiftFormat for Xcode icon and search feature
* Hyperphonic - Xcode 12 compatibility for SwiftFormat
* Maxime Marinel - Git pre-commit hook script
* Romain Pouclet - Homebrew formula
* Aerobounce - Homebrew cask and Sublime Text plugin
* Facundo Menzella - Several new formatting rules and options
* Ali Akhtarzada - Several path-related CLI enhancements
* Yonas Kolb - Swift Package Manager integration
* Wolfgang Lutz - AppleScript integration instructions
* Balázs Kilvády - Xcode lint warning integration
* Anthony Miller - Improvements to wrap/indent logic
* Shingo Takagi - Several brace-related bug fixes
* Benedek Kozma - Lint-only rules option
* Juri Pakaste - Filelist feature
* Jim Puls - Big Sur icon update
* Daniele Formichelli - JSON reporter
* Jonas Boberg - Github actions log reporter
* Mahdi Bchatnia - Linux build workflow
* Saleem Abdulrasool - Windows build workflow
* Arthur Semenyutin - Docker image
* Marco Eidinger - Swift Package Manager plugin
* Hampus Tågerud - Git integration for fileHeader rule
* Nick Lockwood - Everything else

(Full list of contributors)