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.

Sign up for GitHub

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

Jump to bottom

Don't WARN when a spec matches no relevant targets. #14904

Merged
merged 1 commit into from
Apr 5, 2022
Merged

Don't WARN when a spec matches no relevant targets. #14904

merged 1 commit into from
Apr 5, 2022

Commits on Apr 3, 2022

  1. Don't warn if no relevant targets in glob or --changed. 

    In these cases, the user intent is likely "if there are relevant
targets, act on them", so warning is just annoying.

However we still want to retain the warning if the user provided
literal addresses, filesystem specs, or no specs at all.

[ci skip-rust]

[ci skip-build-wheels]
    @benjyw
    benjyw committed Apr 3, 2022
    Configuration menu
    Copy the full SHA
    9ddf6bb View commit details
    Browse the repository at this point in the history