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
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -361,6 +361,13 @@ By doing this you won't create new issues in code and can smoothly fix existing
361
361
A: You have 2 choices:
362
362
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).
363
363
2. Use custom CI: just run `golangci-lint` in CI and check exit code. If it's non-zero - fail the build. The main disadvantage is that you can't see found issues in pull request code and should view build log, then open needed source file to see a context.
364
+
If you'd like to vendor `golangci-lint` to fix it's version run:
365
+
```bash
366
+
go get -u github.com/golang/dep/cmd/dep
367
+
dep init
368
+
dep ensure -v -add github.com/golangci/golangci-lint/cmd/golangci-lint
369
+
```
370
+
And in CI run next command to install vendored `golangci-lint`: `go install ./vendor/github.com/golangci/golangci-lint/cmd/golangci-lint/`.
364
371
365
372
**Q: `golangci-lint` doesn't work**
366
373
1. Update it: `go get -u github.com/golangci/golangci-lint/cmd/golangci-lint`
0 commit comments