Print verbose info during PR validation (target: 'develop' branch)
- Show the version of the spec-parser currently working with
- Add
--debug--verboseto spec-parser options to print more information for the PR author to understand why the purposed changes failed the validation (if it failed)
What is the purpose of the "validation"? I assume to make sure that the input is "correct" / "valid".
What does this mean? More specifically:
- errors should most definitely be flagged
- what about warnings?
And how is it checked?
- is only the exit code of the process?
- or is the generated output / error messages also checked?
If it's valid it's good.
If it's not, having some information to understand why it is the case is good.
@bact - Can you rebase to trigger the CI? The old CI failed, but it is too stale to see the logs
@zvr - any concerns about merging?
Thanks. I will rebase / check the parameters again to keep up with latest spec-parser.
Looks like this is still failing the CI
@bact - can you check?