Skip to content

Conversation

keith
Copy link

@keith keith commented May 30, 2024

It's possible that users don't have a bazel in their path depending on your project configuration. This allows passing --bazel whatever to override to a custom wrapper, or anything else.

It's possible that users don't have a `bazel` in their path depending on
your project configuration. This allows passing `--bazel whatever` to
override to a custom wrapper, or anything else.
@cpsauer
Copy link
Contributor

cpsauer commented Jun 29, 2024

(For any other readers: Centralizing discussion over in #191, since you'd expressed a preference for that one.)

@keith
Copy link
Author

keith commented Aug 29, 2024

closing for that one

@keith keith closed this Aug 29, 2024
@keith keith deleted the ks/allow-overriding-bazel-executable branch August 29, 2024 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants