Skip to content

Commit 52abf48

Browse files
committed
chore: revert golangci#3506
1 parent debc0a3 commit 52abf48

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

docs/src/docs/contributing/new-linters.mdx

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -83,8 +83,11 @@ If you're looking for instructions on how to configure your own custom linter, t
8383
8484
That is all the configuration that is required to run a custom linter in your project.
8585
86-
Custom linters are disabled by default, and are not enabled when `linters.enable-all` is specified.
87-
They can be enabled by adding them the `linters.enable` list, or providing the enabled option on the command line (`golangci-lint run -Eexample`).
86+
Custom linters are enabled by default, but abide by the same rules as other linters.
87+
88+
If the disable all option is specified either on command line or in `.golang.yml` files `linters.disable-all: true`, custom linters will be disabled;
89+
they can be re-enabled by adding them to the `linters:enable` list,
90+
or providing the enabled option on the command line, `golangci-lint run -Eexample`.
8891

8992
The configuration inside the `settings` field of linter have some limitations (there are NOT related to the plugin system itself):
9093
we use Viper to handle the configuration but Viper put all the keys in lowercase, and `.` cannot be used inside a key.

0 commit comments

Comments
 (0)