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: docs/src/docs/contributing/workflow.mdx
+4-4
Original file line number
Diff line number
Diff line change
@@ -45,20 +45,20 @@ Push your branch to your `golangci-lint` fork and open a pull request against th
45
45
46
46
## Pull request checks
47
47
48
-
First, please, accept [CLA](https://gist.github.com/jirfag/26a39fd375da84b2d5ad4296fecb0668) - [cla assistant](https://cla-assistant.io/) will make a comment on the pull request about it.
48
+
First, please, accept [CLA](https://gist.github.com/jirfag/26a39fd375da84b2d5ad4296fecb0668) - [CLA assistant](https://cla-assistant.io/) will make a comment on the pull request about it.
49
49
50
-
Also, we run a few checks in CI by using GitHub actions, you can see them [here](https://github.com/golangci/golangci-lint/blob/master/.github/workflows/pr.yml).
50
+
Also, we run a few checks in CI by using GitHub Actions, you can see them [here](https://github.com/golangci/golangci-lint/blob/master/.github/workflows/pr.yml).
51
51
52
52
## New releases
53
53
54
54
First, see [our versioning policy](/product/roadmap/#versioning-policy).
55
55
56
56
To make a new release create a tag `vx.y.z`. Don't forget to add zero patch version for a new minor release, e.g. `v1.99.0`.
57
-
A GitHub action[workflow](https://github.com/golangci/golangci-lint/blob/master/.github/workflows/tag.yml) will start building and publishing release after that.
57
+
A GitHub Action[workflow](https://github.com/golangci/golangci-lint/blob/master/.github/workflows/tag.yml) will start building and publishing release after that.
58
58
59
59
After making a release you need to update:
60
60
61
-
1. GitHub [action config](https://github.com/golangci/golangci-lint/blob/master/assets/github-action-config.json) by running:
61
+
1. GitHub [Action config](https://github.com/golangci/golangci-lint/blob/master/assets/github-action-config.json) by running:
Copy file name to clipboardExpand all lines: docs/src/docs/plugins/go-plugins.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ An example linter can be found at [here](https://github.com/golangci/example-plu
48
48
If you're looking for instructions on how to configure your own custom linter, they can be found further down.
49
49
50
50
1. If the project you want to lint does not have one already, copy the [.golangci.yml](https://github.com/golangci/golangci-lint/blob/master/.golangci.yml) to the root directory.
51
-
2. Adjust the yaml to appropriate `linters-settings.custom` entries as so:
51
+
2. Adjust the YAML to appropriate `linters-settings.custom` entries as so:
curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s {.LatestVersion}
38
38
39
-
# In alpine linux (as it does not come with curl by default)
39
+
# In Alpine Linux (as it does not come with curl by default)
40
40
wget -O- -nv https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s {.LatestVersion}
41
41
42
42
golangci-lint --version
@@ -62,7 +62,7 @@ On Windows, you can run the above commands with Git Bash, which comes with [Git
62
62
63
63
Golangci-lint is available inside the majority of the package managers.
64
64
65
-
### MacOS
65
+
### macOS
66
66
67
67
#### Brew
68
68
@@ -76,19 +76,19 @@ brew install golangci-lint
76
76
brew upgrade golangci-lint
77
77
```
78
78
79
-
Note: Previously we used a [homebrew tap](https://github.com/golangci/homebrew-tap). We recommend using official formula instead of the tap, but sometimes the most recent release
80
-
isn't immediately available via homebrew core due to manual updates that need to occur from homebrew core maintainers. In this case, the tap formula, which is updated automatically,
79
+
Note: Previously we used a [Homebrew tap](https://github.com/golangci/homebrew-tap). We recommend using official formula instead of the tap, but sometimes the most recent release
80
+
isn't immediately available via Homebrew core due to manual updates that need to occur from Homebrew core maintainers. In this case, the tap formula, which is updated automatically,
81
81
can be used to install the latest version of `golangci-lint`:
82
82
83
83
```sh
84
84
brew tap golangci/tap
85
85
brew install golangci/tap/golangci-lint
86
86
```
87
87
88
-
#### Macports
88
+
#### MacPorts
89
89
90
-
It can also be installed through [macports](https://www.macports.org/)
91
-
The macports installation mode is community driven, and not officially maintained by golangci team.
90
+
It can also be installed through [MacPorts](https://www.macports.org/)
91
+
The MacPorts installation mode is community driven, and not officially maintained by golangci team.
Copy file name to clipboardExpand all lines: pkg/golinters/nolintlint/internal/README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# nolintlint
2
2
3
3
nolintlint is a Go static analysis tool to find ill-formed or insufficiently explained `//nolint` directives for golangci-lint
4
-
(or any other linter, using this package)
4
+
(or any other linter, using this package)
5
5
6
6
## Purpose
7
7
@@ -15,7 +15,7 @@ func hash(data []byte) []byte {
15
15
}
16
16
```
17
17
18
-
In the above case, nolint directives are present but the user has no idea why this is being done or which linter
18
+
In the above case, nolint directives are present, but the user has no idea why this is being done or which linter
19
19
is being suppressed (in this case, gosec recommends against use of md5). `nolintlint` can require that the code provide an explanation, which might look as follows:
20
20
21
21
```Go
@@ -26,6 +26,6 @@ func hash(data []byte) []byte {
26
26
}
27
27
```
28
28
29
-
`nolintlint` can also identify cases where you may have written `// nolint`. Finally `nolintlint`, can also enforce that you
29
+
`nolintlint` can also identify cases where you may have written `// nolint`. Finally,`nolintlint`, can also enforce that you
30
30
use the machine-readable nolint directive format `//nolint:all` and that you mention what linter is being suppressed, as shown above when we write `//nolint:gosec`.
0 commit comments