justingrote/Super Duper Linter
Lints and validates code files in your repository, very helpful for Pull Requests!
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| linter | Name(s) of the linters you wish to run. Runs all by default | no | — |
| customLinterPath | Specify a relative path within your repository that contains the custom linters. Defaults to "linters". These definitions will OVERRIDE (not merge) definitions of the same name. | no | — |
| path | Specify a relative path of your repository to lint. Only files in this path will be processed | no | — |
| excludepath | Explicit file paths to exclude, relative to your root directory. Wildcards are *not* supported | no | — |
| include | Files patterns to include. Wildcards are supported. | no | — |
| exclude | Files patterns to exclude. Wildcards are supported. | no | — |
| debug | Set to True to enable advanced Powershell-level debugging | no | — |
| verbose | Set to True to enable advanced Powershell-level verbose logging | no | — |
| problemsOnly | Set to True to only display problems in the test result output | no | — |
| parallel | Set to the number of linters to run concurrently. By default this is set to the number of logical cores in your system plus 1 | no | — |
| all | Set to True to evaluate all files in the repository, not just those that have changed since the last PR | no | — |
| test | Set to true to validate the linter operation against defined test cases. This is useful if defining a new custom linter. | no | — |
| severity | Choose what level of issue severity consistutes a failure of the linter and that it should exit with a non-zero exit status. Options are error, warning, and information. Options are inclusive of their previous choices (e.g. setting information also fails on warnings and errors) | no | — |
Outputs
| name | description |
|---|---|
| result | A JSON representation of the linter results |