Repository navigation
feat: add output_name input to map KICS --output-name CLI option - #154
Conversation
daed6b1 to
e28e162
Compare
|
Not sure what is the process here |
- Pass --output-name as a single argument so a name with spaces is not split. - Drop a trailing .json from the name, KICS appends the extension itself. - Resolve the entrypoint.sh conflict with the path flags now kept in "$@". - Remove the output_name entry from args, nothing reads positional arguments. - Document output_name in the README. - Cover the flag, the report lookup and the cleanup with tests.
|
Thanks for this @rasta-rocket! |
LGTM You can proceed @cx-artur-ribeiro 👍 |
Summary
Adds the missing
output_nameinput to the GitHub Action, mapping it to theKICS CLI
--output-nameflag. This allows users to customize the name of theresults output file instead of relying on the default.
Changes
output_nameinput inaction.yml(grouped with other output-related inputs)action.ymlINPUT_OUTPUT_NAMEto--output-nameinentrypoint.shkics scancommandentrypoint.shto use the custom filename when resolving thecopy path (
CP_PATH) instead of hardcodingresults.jsonprocessOutputPath()insrc/main.jsto build the JSON resultsfile path using the custom name, so that post-scan features (annotations,
PR comments, job summary) read the correct file