eeafj/golangci-lint
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 1 Wiki Activity

Remove reference to golangci.com in README (#997)

Browse Source 
This project is shutting down on the 15th April. See the blog below:
https://medium.com/golangci/golangci-com-is-closing-d1fc1bd30e0e
This commit is contained in:
Wilkins 2020-05-05 16:26:02 +01:00 committed by GitHub
parent 38782dd097
commit ca04ca6b59
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -1269,10 +1269,7 @@ By doing this you won't create new issues in your code and can choose fix existi
**How to use `golangci-lint` in CI (Continuous Integration)?** **How to use `golangci-lint` in CI (Continuous Integration)?**
You have 2 choices: Run `golangci-lint` in CI and check the exit code. If it's non-zero - fail the build.
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).
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.
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. 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.

5
README.tmpl.md
View File

@ -581,10 +581,7 @@ By doing this you won't create new issues in your code and can choose fix existi
**How to use `golangci-lint` in CI (Continuous Integration)?** **How to use `golangci-lint` in CI (Continuous Integration)?**
You have 2 choices: Run `golangci-lint` in CI and check the exit code. If it's non-zero - fail the build.
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).
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.
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. 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.