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: code-quality/linters/supported/README.md
+68-5
Original file line number
Diff line number
Diff line change
@@ -4,14 +4,77 @@ description: Trunk Code Quality supports over 100 linters and formatters
4
4
5
5
# Supported Linters
6
6
7
-
{% hint style="info" %}
8
-
📘 Our linter integrations are open-source!
9
-
10
-
You can find them at [`trunk-io/plugins`](https://github.com/trunk-io/plugins).
11
-
{% endhint %}
7
+
> 📘 Our linter integrations are open-source!
8
+
>
9
+
> You can find them at [`trunk-io/plugins`](https://github.com/trunk-io/plugins).
12
10
13
11
Enable any of the following tools with:
14
12
15
13
```
16
14
trunk check enable <linter>
17
15
```
16
+
17
+
[//]: #
18
+
[//]: #"1. Support for Detekt is under active development; see our [docs](https://docs.trunk.io/docs/code-quality/supported-linters#detekt) for more details."
19
+
[//]: #"2. [Module inspection](https://github.com/terraform-linters/tflint/blob/master/docs/user-guide/module-inspection.md), [deep checking](https://github.com/terraform-linters/tflint-ruleset-aws/blob/master/docs/deep_checking.md), and setting variables are not currently supported."
20
+
[//]: #
21
+
[//]: #"### Linter-specific Configuration"
22
+
[//]: #
23
+
[//]: #"Some linters require a bit more modification to properly set up. View page for the particular linter for more info."
24
+
25
+
| Technology | Linters |
26
+
| ---------- | ------- |
27
+
| All |[codespell](./codespell.md), [cspell](./cspell.md), [git-diff-check](./git-diff-check.md), [gitleaks](./gitleaks.md), [pre-commit-hooks](./pre-commit-hooks.md)|
Copy file name to clipboardexpand all lines: code-quality/linters/supported/ansible-lint.md
+12-9
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,6 @@
1
1
---
2
-
description: >-
3
-
Checks playbooks for practices and behavior that could potentially be improved
4
-
and can fix some of the most common ones for you
2
+
description: Checks playbooks for practices and behavior that could potentially be improved and can fix some of the most common ones for you
3
+
title: Trunk | How to run Ansible-lint
5
4
layout:
6
5
title:
7
6
visible: true
@@ -32,19 +31,23 @@ Ansible-lint will never be auto-enabled. It must be enabled manually.
32
31
## Settings
33
32
34
33
Ansible-lint supports the following config files:
35
-
36
34
*`.ansible-lint`
37
35
38
-
You can move these files to `.trunk/configs` and `trunk check` will still find them. See [Moving Linter Configs](broken-reference) for more info.
36
+
You can move these files to `.trunk/configs` and `trunk check` will still find them. See [Moving Linter Configs](..#moving-linter-configs) for more info.
37
+
39
38
40
39
## Usage Notes
41
40
42
-
**Ansible-lint** must be configured with a trigger. See the [trigger rules](broken-reference) documentation for more information.
41
+
**Ansible-lint** must be configured with a trigger. See the [trigger rules](../#trigger-rules) documentation for more information.
43
42
44
43
If your ansible setup is not contained within a single folder you would list all files and directories belonging to your ansible setup.
Copy file name to clipboardexpand all lines: code-quality/linters/supported/autopep8.md
+9-8
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
---
2
2
description: autopep8 is a linter for Python
3
+
title: Trunk | How to run autopep8
3
4
layout:
4
5
title:
5
6
visible: true
@@ -22,23 +23,23 @@ You can enable the autopep8 linter with:
22
23
```shell
23
24
trunk check enable autopep8
24
25
```
25
-
26
-

27
-
26
+

28
27
## Auto Enabling
29
28
30
29
autopep8 will be auto-enabled if a `.pep8` config file is present.
31
30
32
31
## Settings
33
32
34
33
autopep8 supports the following config files:
35
-
36
34
*`.pep8`
37
35
38
-
You can move these files to `.trunk/configs` and `trunk check` will still find them. See [Moving Linter Configs](broken-reference) for more info.
36
+
You can move these files to `.trunk/configs` and `trunk check` will still find them. See [Moving Linter Configs](..#moving-linter-configs) for more info.
Copy file name to clipboardexpand all lines: code-quality/linters/supported/bandit.md
+11-13
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,6 @@
1
1
---
2
-
description: >-
3
-
Bandit is a security linter for Python codebases. Bandit flags problems like
4
-
hard-coded passwords, injection vulnerabilities, and the use of insecure
5
-
libraries.
2
+
description: Bandit is a security linter for Python codebases. Bandit flags problems like hard-coded passwords, injection vulnerabilities, and the use of insecure libraries.
3
+
title: Trunk | How to run Bandit
6
4
layout:
7
5
title:
8
6
visible: true
@@ -25,23 +23,23 @@ You can enable the Bandit linter with:
25
23
```shell
26
24
trunk check enable bandit
27
25
```
28
-
29
-

30
-
26
+

31
27
## Auto Enabling
32
28
33
-
Bandit will be auto-enabled if any _Python_ files are present.
29
+
Bandit will be auto-enabled if any *Python* files are present.
34
30
35
31
## Settings
36
32
37
33
Bandit supports the following config files:
38
-
39
34
*`.bandit`
40
35
41
-
You can move these files to `.trunk/configs` and `trunk check` will still find them. See [Moving Linter Configs](broken-reference) for more info.
36
+
You can move these files to `.trunk/configs` and `trunk check` will still find them. See [Moving Linter Configs](..#moving-linter-configs) for more info.
Copy file name to clipboardexpand all lines: code-quality/linters/supported/biome.md
+9-6
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
---
2
2
description: biome is a linter for JavaScript, TypeScript, jsx and json
3
+
title: Trunk | How to run biome
3
4
layout:
4
5
title:
5
6
visible: true
@@ -25,19 +26,21 @@ trunk check enable biome
25
26
26
27
## Auto Enabling
27
28
28
-
biome will be auto-enabled if any of its config files are present: _`biome.json`, `rome.json`_.
29
+
biome will be auto-enabled if any of its config files are present: *`biome.json`, `rome.json`*.
29
30
30
31
## Settings
31
32
32
33
biome supports the following config files:
33
-
34
34
*`biome.json`
35
35
*`rome.json`
36
36
37
-
You can move these files to `.trunk/configs` and `trunk check` will still find them. See [Moving Linter Configs](broken-reference) for more info.
37
+
You can move these files to `.trunk/configs` and `trunk check` will still find them. See [Moving Linter Configs](..#moving-linter-configs) for more info.
Copy file name to clipboardexpand all lines: code-quality/linters/supported/brakeman.md
+10-9
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,6 @@
1
1
---
2
-
description: >-
3
-
Brakeman is a static analysis tool designed for Ruby on Rails applications. It
4
-
statically analyzes Rails application code to find security issues.
2
+
description: Brakeman is a static analysis tool designed for Ruby on Rails applications. It statically analyzes Rails application code to find security issues.
3
+
title: Trunk | How to run Brakeman
5
4
layout:
6
5
title:
7
6
visible: true
@@ -27,18 +26,20 @@ trunk check enable brakeman
27
26
28
27
## Auto Enabling
29
28
30
-
Brakeman will be auto-enabled if any _Ruby_ files are present.
29
+
Brakeman will be auto-enabled if any *Ruby* files are present.
31
30
32
31
## Settings
33
32
34
33
Brakeman supports the following config files:
35
-
36
34
*`brakeman.ignore`
37
35
38
-
You can move these files to `.trunk/configs` and `trunk check` will still find them. See [Moving Linter Configs](broken-reference) for more info.
36
+
You can move these files to `.trunk/configs` and `trunk check` will still find them. See [Moving Linter Configs](..#moving-linter-configs) for more info.
0 commit comments