Exit with accurate signal depending report result #2
Description
Is your feature request related to a problem? Please describe.
Command for tools that are making check or analyze commonly use a proper Signal exit code when there is an error so it can be used as an alert or a blocker when it is include into job suite like in CI.
Currently dependency-comb always exit signal "0", meaning it is always a success.
Describe the solution you'd like
To be used in a CI or another job suite the report command should exit with a more accurate exit signal which should probably code 1.
However currently i don't know yet when to use this signal. Is this should be just when there is a lateness from any package ? Or for a certain amount of lateness in a package (like with 5 version lateness) ? Or about date age ? If this is something more precise than just "any single version lateness from any package" it would certainly need an option to define it from user, this could not be something hardcoded.
What i'm sure is:
- This behavior will only be for the 'report' command, analyze and format should still always use the signal 0;
- Any requirement parsing failures would lead to exit signal 1, however it won't happen if failures report are disabled;
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.