I have removed the “custom” command as it didn’t really serve to shorten anything for the end user. I then also added a job for “analyze” which I believe is what your original example set out to achieve. This is a job that can be added to a workflow which will checkout the users code, install the fossa CLI using your setup command, and then run “fossa analyze”. I added the ability to also save those results as an artifact and enable debugging based on some parameters. Saving to an artifact should be on by default.
Missing:
Need to address authentication. Either by adding a parameter if fed to the CLI, or making a note withing the setup description.
I have removed the “custom” command as it didn’t really serve to shorten anything for the end user. I then also added a job for “analyze” which I believe is what your original example set out to achieve. This is a job that can be added to a workflow which will checkout the users code, install the fossa CLI using your setup command, and then run “fossa analyze”. I added the ability to also save those results as an artifact and enable debugging based on some parameters. Saving to an artifact should be on by default.
Missing:
Need to address authentication. Either by adding a parameter if fed to the CLI, or making a note withing the setup description.
Check all description
Tasks: