bamaer opened a new issue, #8826: URL: https://github.com/apache/hop/issues/8826
### What would you like to happen? ### What A workflow action that lints a project or a folder, and succeeds or fails on a severity threshold. It uses the same engine, the same rule packs and the same `hop-lint.yml` as `hop lint`, so the two can never disagree. **Options** (mirroring the command line): | Option | Default | Same as | |---|---|---| | Project or folder | current project | `<file\|directory>` | | Include metadata | yes | — | | Config file | the project's `hop-lint.yml` | `--config` | | Minimum severity | INFO | `--severity` | | Fail on | ERROR | `--fail-on` (ERROR, WARNING, NONE) | | Max warnings | empty | `--max-warnings` | | Baseline file | empty | `--baseline` | | Report file | empty | `--output` | | Report format | SARIF | `--format` (TEXT, JSON, SARIF) | **Result** - The action succeeds or fails according to the thresholds. - One result row per finding. - Variables for the actions that follow: `LINT_ERRORS`, `LINT_WARNINGS`, `LINT_INFOS`, `LINT_REPORT_FILE`. - The report file is added to the result files, so a Mail action can attach it. ### Why A scheduled or pre-deployment lint becomes an ordinary workflow that runs on Hop Server and in containers, without wrapping `hop lint` in a shell action. The name "Run Linter" avoids confusion with the "Lint Project" entry in Hop GUI's menu. ### Done when - The action and `hop lint` give identical findings and exit status on the same project. - It runs headless (Hop Server, containers) without touching GUI classes. - A broken rule pack fails the action with the pack's own error message. ### Issue Priority Priority: 2 ### Issue Component Component: Actions -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
