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

doc: remove from FAQ golangci.com mention (#3655)

Browse Source
This commit is contained in:
Oleksandr Redko 2023-03-04 00:13:05 +02:00 committed by GitHub
parent ad334b0650
commit dc799dcfc1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/src/docs/usage/faq.mdx
View File

@ -9,7 +9,7 @@ Or you can create a [GitHub Issue](https://github.com/golangci/golangci-lint/iss
## How to integrate `golangci-lint` into large project with thousands of issues ## How to integrate `golangci-lint` into large project with thousands of issues
We are sure that every project can easily integrate `golangci-lint`, even the large one. The idea is to not fix all existing issues. Fix only newly added issue: issues in new code. To do this setup CI (or better use [GolangCI](https://golangci.com)) to run `golangci-lint` with option `--new-from-rev=HEAD~1`. Also, take a look at option `--new`, but consider that CI scripts that generate unstaged files will make `--new` only point out issues in those files and not in the last commit. In that regard `--new-from-rev=HEAD~1` is safer. We are sure that every project can easily integrate `golangci-lint`, even the large one. The idea is to not fix all existing issues. Fix only newly added issue: issues in new code. To do this setup CI to run `golangci-lint` with option `--new-from-rev=HEAD~1`. Also, take a look at option `--new`, but consider that CI scripts that generate unstaged files will make `--new` only point out issues in those files and not in the last commit. In that regard `--new-from-rev=HEAD~1` is safer.
By doing this you won't create new issues in your code and can choose fix existing issues (or not). By doing this you won't create new issues in your code and can choose fix existing issues (or not).
## How to use `golangci-lint` in CI ## How to use `golangci-lint` in CI