Skip to content

Commit 635cf89

Browse files
authored
docs: update install from sources paragraph (#5397)
1 parent f5396bd commit 635cf89

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

docs/src/docs/welcome/install.mdx

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -134,18 +134,18 @@ docker run -t --rm -v $(pwd):/app -w /app golangci/golangci-lint:{.LatestVersion
134134

135135
### Install from Sources
136136

137-
Such `go install`/`go get`, "tools pattern", and `tool` command/directives installations aren't guaranteed to work.
137+
Using `go install`/`go get`, "tools pattern", and `tool` command/directives installations aren't guaranteed to work.
138138

139139
We recommend using binary installation.
140140

141-
Those installations aren't recommended because of the following points:
141+
These installations aren't recommended because of the following points:
142142

143-
1. Those installations are compiling golangci-lint locally, the Go version used to build will depend on your local Go version.
144-
2. Some users use `-u` flag for `go get`, which upgrades our dependencies. Resulting binary was not tested and is not guaranteed to work.
145-
3. When using "tools pattern" or and `tool` command/directives, the dependencies of a tool can modify the dependencies of another or your project. Resulting binary was not tested and is not guaranteed to work.
146-
4. We've encountered issues with Go modules hashes due to unexpected recreation of dependency tags.
147-
5. `go.mod` replacement directives don't apply transitively. It means a user will be using patched version of `golangci-lint` if we use such replacements.
148-
6. It allows installation from main branch which can't be considered stable.
143+
1. These installations compile golangci-lint locally. The Go version used to build will depend on your local Go version.
144+
2. Some users use the `-u` flag for `go get`, which upgrades our dependencies. The resulting binary was not tested and is not guaranteed to work.
145+
3. When using the "tools pattern" or `tool` command/directives, the dependencies of a tool can modify the dependencies of another tool or your project. The resulting binary was not tested and is not guaranteed to work.
146+
4. We've encountered issues with Go module hashes due to the unexpected recreation of dependency tags.
147+
5. `go.mod` replacement directives don't apply transitively. It means a user will be using a patched version of `golangci-lint` if we use such replacements.
148+
6. It allows installation from the main branch, which can't be considered stable.
149149
7. It's slower than binary installation.
150150

151151
```sh

0 commit comments

Comments
 (0)