Repository navigation
feat(cli): add --report and --report-path to write report files - #124
Merged
Merged
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



What
--reportwrites the report to files and keeps the table on screen;--report-pathsays where.-otakes several formats, comma-separated, with--report: json, markdown and sarif go to files, table or github stays on screen, and the table is the default. With no file format in-o,--reportwrites all three (explain: json and Markdown).<command>-<date>.<ext>; a second run on the same day replaces them, and the time is in the report. Missing directories are created. Each file written is printed on stderr.--report,-otakes one format on stdout as before, so-o json | jqkeeps working.--output-fileis still accepted but hidden from--help. The GitHub Action keeps using it, so it still works with older releases.Why
--output-filemixed two things in one flag: a plain path replaced stdout with the-oformat, andFORMAT=FILEadded a file. Getting the usual CI set (table in the log, Markdown for the pull request, SARIF for code scanning) took one--output-file FORMAT=FILEper file, with names chosen by hand.Type
Checklist
go test ./...)docs/, ordocs/clivia gendocs)