aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbodqhrohro <bodqhrohro@gmail.com>2020-12-07 13:23:01 +0200
committerGitHub <noreply@github.com>2020-12-07 11:23:01 +0000
commit45dec2059383a7f2f90b75f3b327df3b0309f59e (patch)
treef05c84634c07a24a1a5a86ee9c1175f7cd7b4a6d
parent8f5393db5f4d615452dcc807ddafd4841d9abd5b (diff)
Update links to golangci-lint documentation (#1617)
Signed-off-by: Bohdan Horbeshko <bodqhrohro@gmail.com>
-rwxr-xr-xbuild/scripts/find-lint.sh2
-rw-r--r--docs/CODE_STYLE.md6
2 files changed, 4 insertions, 4 deletions
diff --git a/build/scripts/find-lint.sh b/build/scripts/find-lint.sh
index 7e37e154..eb1b28d8 100755
--- a/build/scripts/find-lint.sh
+++ b/build/scripts/find-lint.sh
@@ -8,7 +8,7 @@
# - `DENDRITE_LINT_CONCURRENCY` - number of concurrent linters to run,
# golangci-lint defaults this to NumCPU
# - `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.
diff --git a/docs/CODE_STYLE.md b/docs/CODE_STYLE.md
index 8f1c1cb5..8096ae27 100644
--- a/docs/CODE_STYLE.md
+++ b/docs/CODE_STYLE.md
@@ -2,13 +2,13 @@
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).
-[Installation](https://github.com/golangci/golangci-lint#install) and [Editor
-Integration](https://github.com/golangci/golangci-lint#editor-integration) for
+[Installation](https://github.com/golangci/golangci-lint#install-golangci-lint) and [Editor
+Integration](https://golangci-lint.run/usage/integrations/#editor-integration) for
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 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
when its clear that the lint warning is spurious.