nimba-actions/SFDX Scan Pull Request
Executes SFDX Scanner on the scope of a pull request, translates the findings into in-line comments.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| category | Categor(ies) of rules to run. | — | — |
| engine | Engine(s) to run. | — | — |
| eslint-env | JSON-formatted string, overrides ESLint's default environment variables. | — | — |
| eslintconfig | Location of eslintrc config to customize eslint engine. | — | — |
| pmdconfig | Location of PMD rule reference XML file to customize rule selection. | — | — |
| custom-pmd-rules | JSON string which defines any custom rules which need to be registered before the scan is ran. Custom rules are identified by the path to their XML/JAR file and their language. | — | — |
| severity-threshold | Integer threshold value which will throw an error when violations of specific severity (or more severe) are detected. | — | — |
| strictly-enforced-rules | JSON string which contains the rules which will be strictly enforced regardless of their priority. Enforced rules are identified by their engine, category, and rule name. | — | — |
| target | Optional target to specify a whole directory to run, as opposed to just the diff of a pull request | — | — |
| tsconfig | Location of tsconfig.json file. | — | — |
| report-mode | Use comments or check-runs for reporting errors | — | check-runs |
| delete-resolved-comments | Set `true` to delete comments once the issue has been resolved | — | false |
Outputs
no outputs