You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-4
Original file line number
Diff line number
Diff line change
@@ -1269,10 +1269,7 @@ By doing this you won't create new issues in your code and can choose fix existi
1269
1269
1270
1270
**How to use `golangci-lint` in CI (Continuous Integration)?**
1271
1271
1272
-
You have 2 choices:
1273
-
1274
-
1. Use [GolangCI](https://golangci.com): this service is highly integrated with GitHub (issues are commented in the pull request) and uses a `golangci-lint` tool. For configuration use `.golangci.yml` (or toml/json).
1275
-
2. Use custom CI: just run `golangci-lint` in CI and check the exit code. If it's non-zero - fail the build. The main disadvantage is that you can't see issues in pull request code and would need to view the build log, then open the referenced source file to see the context.
1272
+
Run `golangci-lint` in CI and check the exit code. If it's non-zero - fail the build.
1276
1273
1277
1274
We don't recommend vendoring `golangci-lint` in your repo: you will get troubles updating `golangci-lint`. Please, use recommended way to install with the shell script: it's very fast.
Copy file name to clipboardExpand all lines: README.tmpl.md
+1-4
Original file line number
Diff line number
Diff line change
@@ -581,10 +581,7 @@ By doing this you won't create new issues in your code and can choose fix existi
581
581
582
582
**How to use `golangci-lint` in CI (Continuous Integration)?**
583
583
584
-
You have 2 choices:
585
-
586
-
1. Use [GolangCI](https://golangci.com): this service is highly integrated with GitHub (issues are commented in the pull request) and uses a `golangci-lint` tool. For configuration use `.golangci.yml` (or toml/json).
587
-
2. Use custom CI: just run `golangci-lint` in CI and check the exit code. If it's non-zero - fail the build. The main disadvantage is that you can't see issues in pull request code and would need to view the build log, then open the referenced source file to see the context.
584
+
Run `golangci-lint` in CI and check the exit code. If it's non-zero - fail the build.
588
585
589
586
We don't recommend vendoring `golangci-lint` in your repo: you will get troubles updating `golangci-lint`. Please, use recommended way to install with the shell script: it's very fast.
0 commit comments