Skip to content

Commit ca04ca6

Browse files
authored
Remove reference to golangci.com in README (#997)
This project is shutting down on the 15th April. See the blog below: https://medium.com/golangci/golangci-com-is-closing-d1fc1bd30e0e
1 parent 38782dd commit ca04ca6

File tree

2 files changed

+2
-8
lines changed

2 files changed

+2
-8
lines changed

README.md

+1-4
Original file line numberDiff line numberDiff line change
@@ -1269,10 +1269,7 @@ By doing this you won't create new issues in your code and can choose fix existi
12691269
12701270
**How to use `golangci-lint` in CI (Continuous Integration)?**
12711271
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.
12761273
12771274
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.
12781275

README.tmpl.md

+1-4
Original file line numberDiff line numberDiff line change
@@ -581,10 +581,7 @@ By doing this you won't create new issues in your code and can choose fix existi
581581

582582
**How to use `golangci-lint` in CI (Continuous Integration)?**
583583

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.
588585

589586
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.
590587

0 commit comments

Comments
 (0)