Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Is it possible to do some sort of dry run and have pants report which files have changed and will require further action?

and it doesn't have to be super precise or detailed, but at the same level of the cache knowing "oh, somethign is different here" I'd love to be able to run a `pants dirty src/cmd:files` to have it show what it detected has changed

```pants --changed-since=$commit_ref --filter-target-type=files list```
this will list all `files` targets changed since `$commit_ref` , e.g. `commit_ref=origin/main`