Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README.md #3995

Merged
merged 3 commits into from
Jun 14, 2022
Merged

Update README.md #3995

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
77d8712
Update README.md
itsliamdowd Jun 14, 2022
9b9da67
Update README.md
itsliamdowd Jun 14, 2022
2b38fa6
Update README.md
itsliamdowd Jun 14, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ in your Script Build Phases.
This is the recommended way to install a specific version of SwiftLint since it supports
installing a pinned version rather than simply the latest (which is the case with Homebrew).

Note that this will add the SwiftLint binaries, its dependencies' binaries and the Swift binary
Note that this will add the SwiftLint binaries, its dependencies' binaries, and the Swift binary
library distribution to the `Pods/` directory, so checking in this directory to SCM such as
git is discouraged.

Expand Down Expand Up @@ -113,7 +113,7 @@ results.

If you wish to fix violations as well, your script could run
`swiftlint --fix && swiftlint` instead of just `swiftlint`. This will mean
that all correctable violations are fixed, while ensuring warnings show up in
that all correctable violations are fixed while ensuring warnings show up in
your project for remaining violations.

If you've installed SwiftLint via CocoaPods the script should look like this:
Expand Down Expand Up @@ -374,7 +374,7 @@ run SwiftLint from. The following parameters can be configured:
Rule inclusion:

* `disabled_rules`: Disable rules from the default enabled set.
* `opt_in_rules`: Enable rules not from the default set.
* `opt_in_rules`: Enable rules that are not part of the default set.
* `only_rules`: Only the rules specified in this list will be enabled.
Cannot be specified alongside `disabled_rules` or `opt_in_rules`.
* `analyzer_rules`: This is an entirely separate list of rules that are only
Expand Down Expand Up @@ -634,7 +634,7 @@ specifications of nested configurations are getting ignored because there's no s
If one (or more) SwiftLint file(s) are explicitly specified via the `--config` parameter,
that configuration will be treated as an override, no matter whether there exist
other `.swiftlint.yml` files somewhere within the directory. **So if you want to use
use nested configurations, you can't use the `-- config` parameter.**
nested configurations, you can't use the `--config` parameter.**

## License

Expand Down