Skip to content

CLI always return exit code 1 #130

Open
@L4ngu0r

Description

@L4ngu0r

Related issues in timeline order:

I think that the convention accross program is that Exit code 1 is use for errors.
If you want to use it in a CI, for instance, it will always fail.

Another approach would be to keep the exit code 0 and provide more details output on if their is changes or not, or catch real errors and then exit code 1.
Using exit code was cheap and fast, but it doesn't really follow the usage of command line in general.

What do you think?

For reference:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions