Would be really practical for PR Reviews if we could "@validator-bot $jsonfilepath(s)" and get the validator output as a reply 馃憖
Args could be like "botname validate [latest, $tag, pr, ...] -T [presets for cli, exp full or 6.1.1] [test filenames whitespace seperated]
We should do strict filename parsing (only filenames, no paths, adheres to known 2 filename schema), same for test ids
Then match on the filenames in the two known directories, no wildcards or similar.
We could, in a GH action, either pull the csaf validator or build the PR one, then run the files, then return the input as comment.
Only to be called by project team members, and to run without the 6.3.6/6.3.7 (and probably others)
I look forward to your thoughts, I think this could really improve our DX
Would be really practical for PR Reviews if we could "@validator-bot $jsonfilepath(s)" and get the validator output as a reply 馃憖
Args could be like "botname validate [latest, $tag, pr, ...] -T [presets for cli, exp full or 6.1.1] [test filenames whitespace seperated]
We should do strict filename parsing (only filenames, no paths, adheres to known 2 filename schema), same for test ids
Then match on the filenames in the two known directories, no wildcards or similar.
We could, in a GH action, either pull the csaf validator or build the PR one, then run the files, then return the input as comment.
Only to be called by project team members, and to run without the 6.3.6/6.3.7 (and probably others)
I look forward to your thoughts, I think this could really improve our DX