bazel-contrib / target-determinator

Determines which Bazel targets were affected between two git commits.

bazel-contrib/target-determinator Issues

In Bazel 7 diffs involving 3rd party deps seem to be ignored
Updated 2 months ago8
--enforce-clean accepts a tri-state value but only has boolean behaviour
Updated 3 months ago1
Support -enforce-clean=enforce-clean for when the "before" location is unclean
Closed 3 months ago2
TargetHashCache has already been frozen
Updated 3 months ago
Provide an option to override bazel command
Updated 6 months ago2
When using with bzlmod rules_python encounter error with Bazel 6.4.0
Closed 8 months ago
Invalid options syntax error
Updated 9 months ago2
Possible circular configurations?
Closed 10 months ago6
Enhancement: make it possible to print debug logs of what's being hashed
Updated a year ago
target-determinator does not evaluate aliases as changed
Closed a year ago2
Bazel errors with --transitions=lite
Updated a year ago
With Bazel 6 and bzlmod configured rules_python, target determinator complains of invalid characters
Closed a year ago2
deadlock in hashTarget -> build.Target_RULE -> hashRule
Closed a year ago6
targets incompatible with the current platform are selected
Closed a year ago5
bazel-opts are not passed to bazel-config command
Closed a year ago2
[driver] bazel-opts are not passed to test command
Closed a year ago
Add --keep_going flag
Closed a year ago3
Should driver rebuild non-test targets?
Updated a year ago1
Add documentation to build target-determinator & driver from source
Closed a year ago1
Consider exposing an aspect CLI plugin
Updated 2 years ago1
Allow specifying bazel options
Closed 2 years ago
TestDigestsSingleSourceFile fails in clean codespace
Updated 2 years ago
Add an option to avoid updating specifi submodules
Updated 2 years ago12
query for attr does not work
Updated 2 years ago3
CLI support base commit hash file as an input
Updated 2 years ago1