#14128 Improve output when pants-generated targets are used with goals that don't match any files Issue created by thejcannon Is your feature request related to a problem? Please describe. If you're used to running

./pants --changed-since=main fmt lint check test

(or have an alias or whatever) but don't touch any files that match

test

(just as an example). You'll see:

09:23:20.41 [WARN] No applicable files or targets matched. The `test` goal works with these target types:

  * go_package
  * junit_test
  * python_test
  * scala_junit_test
  * scalatest_test
  * shunit2_test

However, you only specified targets with these target types:

  * python_source

This could happen as well if you supply the "target" as a dir which doesn't contain tests as well (so not limited to

--changed-since

). Describe the solution you'd like In these cases, perhaps a no-op output (so maybe neither a green check or a red X). Or the ability to configure what happens. Describe alternatives you've considered N/A Additional context N/A pantsbuild/pants