Skip to content

Exit code 166 if no project affected #128

@cdumange

Description

@cdumange

Hey,

First, thanks a lot for your work, very handy tool you have there !

I'm currently building a CI for a dotnet monorepo. I'm using your tool to help me generate the project to restore/build.
My current problem is that if no project are affected (pipeline stuff, configuration, ...), dotnet affected throws a exit 166 and that messes up the CI steps.

Why is a "no project affected" considered an error ? Shouldn't it be a exit 0 ?

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