char
/
dendrite
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update links to golangci-lint documentation (#1617) 

Signed-off-by: Bohdan Horbeshko <bodqhrohro@gmail.com>
main
bodqhrohro 2020-12-07 13:23:01 +02:00 committed by GitHub
parent 8f5393db5f
commit 45dec20593
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
build/scripts/find-lint.sh
View File

@ -8,7 +8,7 @@
# - `DENDRITE_LINT_CONCURRENCY` - number of concurrent linters to run, # - `DENDRITE_LINT_CONCURRENCY` - number of concurrent linters to run,
# golangci-lint defaults this to NumCPU # golangci-lint defaults this to NumCPU
# - `GOGC` - how often to perform garbage collection during golangci-lint runs. # - `GOGC` - how often to perform garbage collection during golangci-lint runs.
# Essentially a ratio of memory/speed. See https://github.com/golangci/golangci-lint#memory-usage-of-golangci-lint # Essentially a ratio of memory/speed. See https://golangci-lint.run/usage/performance/#memory-usage
# for more info. # for more info.

6
docs/CODE_STYLE.md
View File

@ -2,13 +2,13 @@
In addition to standard Go code style (`gofmt`, `goimports`), we use `golangci-lint` In addition to standard Go code style (`gofmt`, `goimports`), we use `golangci-lint`
to run a number of linters, the exact list can be found under linters in [.golangci.yml](.golangci.yml). to run a number of linters, the exact list can be found under linters in [.golangci.yml](.golangci.yml).
[Installation](https://github.com/golangci/golangci-lint#install) and [Editor [Installation](https://github.com/golangci/golangci-lint#install-golangci-lint) and [Editor
Integration](https://github.com/golangci/golangci-lint#editor-integration) for Integration](https://golangci-lint.run/usage/integrations/#editor-integration) for
it can be found in the readme of golangci-lint. it can be found in the readme of golangci-lint.
For rare cases where a linter is giving a spurious warning, it can be disabled For rare cases where a linter is giving a spurious warning, it can be disabled
for that line or statement using a [comment for that line or statement using a [comment
directive](https://github.com/golangci/golangci-lint#nolint), e.g. `var directive](https://golangci-lint.run/usage/false-positives/#nolint), e.g. `var
bad_name int //nolint:golint,unused`. This should be used sparingly and only bad_name int //nolint:golint,unused`. This should be used sparingly and only
when its clear that the lint warning is spurious. when its clear that the lint warning is spurious.