Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exit with accurate signal depending report result #2

Open
sveetch opened this issue Nov 3, 2024 · 0 comments
Open

Exit with accurate signal depending report result #2

sveetch opened this issue Nov 3, 2024 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@sveetch
Copy link
Owner

sveetch commented Nov 3, 2024

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.

@sveetch sveetch added enhancement New feature or request help wanted Extra attention is needed labels Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant