Closed matejchalk closed 2 days ago
The problem I see here is we would either loose options parsing or have to implement very complicated schema fitting all commands.
I can try to come up with a PoC, maybe put basic core config and keep the options open for additional unspecified fields and document limitations etc.
If it helps, these are commands the GitHub Action relies on or will rely on:
autorun
(implicit, but could be explicit)compare
print-config
merge-diffs
" commandAnd these are the arguments used:
--persist.outputDir
, --persist.filename
and --persist.format
--config
--before
and --after
(only compare
command)merge-diffs
" command will define (e.g. something like --reports .code-pushup/**/report-diff.json
)
The
code-pushup
target needs to accept different commands so that the GitHub Action can use it - see https://github.com/code-pushup/github-action/issues/35#issuecomment-2248507862autorun
from executor command - https://github.com/code-pushup/cli/blob/main/packages/nx-plugin/src/executors/autorun/executor.ts#L26autorun
is implicit, but we can append other commands likecompare
without interference@code-pushup/nx-plugin:autorun
to@code-pushup/nx-plugin:cli