|
3 | 3 |
|
4 | 4 | GolangCI-Lint is a linters aggregator. It's fast: on average [5 times faster](#performance) than gometalinter. It's [easy to integrate and use](#issues-options), has [nice output](#quick-start) and has a minimum number of false positives.
|
5 | 5 |
|
| 6 | +GolangCI-Lint has [integrations](#ide-integrations) with VS Code, GNU Emacs, Sublime Text. |
| 7 | + |
6 | 8 | Sponsored by [GolangCI.com](https://golangci.com): SaaS service for running linters on Github pull requests. Free for Open Source.
|
7 | 9 |
|
8 | 10 | <a href="https://golangci.com/"><img src="docs/go.png" width="250px"></a>
|
@@ -326,9 +328,10 @@ Comment `// nolint` disables all issues reporting on this line. Comment e.g. `//
|
326 | 328 | Please create [GitHub Issues here](https://github.com/golangci/golangci-lint/issues/new) about found false positives. We will add it to default exclude list if it's common or we will fix underlying linter.
|
327 | 329 |
|
328 | 330 | # IDE integrations
|
329 |
| -1. VS Code - [pull request](https://github.com/Microsoft/vscode-go/pull/1693) (thanks to [pdf](https://github.com/pdf)) |
330 |
| -2. vim-go - [issue](https://github.com/fatih/vim-go/issues/1841) |
331 |
| -3. GNU Emacs - [flycheck checker](https://github.com/weijiangan/flycheck-golangci-lint) |
| 331 | +1. VS Code - [pull request](https://github.com/Microsoft/vscode-go/pull/1693) to vscode-go (thanks to [pdf](https://github.com/pdf)). |
| 332 | +2. Vim - [issue](https://github.com/fatih/vim-go/issues/1841) for vim-go. |
| 333 | +3. GNU Emacs - [flycheck checker](https://github.com/weijiangan/flycheck-golangci-lint) (thanks to [weijiangan](https://github.com/weijiangan)). |
| 334 | +4. Sublime Text - [plugin](https://github.com/alecthomas/SublimeLinter-contrib-golang-cilint) for SublimeLinter (thanks to [alecthomas](https://github.com/alecthomas)). |
332 | 335 |
|
333 | 336 | # Internals
|
334 | 337 | The key difference with gometalinter is that golangci-lint shares work between specific linters (golint, govet, ...).
|
@@ -410,3 +413,6 @@ Thanks to developers and authors of used linters:
|
410 | 413 | 8. Minimize false-positives by fixing linters and improving testing tooling.
|
411 | 414 | 9. Automatic issues fixing (code rewrite, refactoring) where it's possible.
|
412 | 415 | 10. Documentation for every issue type.
|
| 416 | + |
| 417 | +# Contact Information |
| 418 | +You can contact the author of GolangCI-Lint by [[email protected]](mailto:[email protected]). |
0 commit comments