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.

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

Flags: discourage the use of absolute in-repo paths for bazel options #75

Merged
merged 1 commit into from
Oct 4, 2023

Conversation

sitaktif
Copy link
Collaborator

@sitaktif sitaktif commented Oct 4, 2023

Document that the user should use the relative form for paths passed to bazel options via --bazel-opts and --bazel-startup-opts.

Target-determinator may query target information in git worktrees, which live in different directories. When this is the case, passing an absolute path in a bazel option, like --bazel-startup-opts=--bazelrc=/my/repo.git/mybazelrc, results in unexpected behaviors if the mybazelrc changed between the "before" and "after" commit.

Document that the user should use the relative form for paths passed to bazel options via `--bazel-opts` and `--bazel-startup-opts`.

Target-determinator may query target information in git worktrees, which live in different directories. When this is the case, passing an absolute path in a bazel option, like `--bazel-startup-opts=--bazelrc=/my/repo.git/mybazelrc`, results in unexpected behaviors if the `mybazelrc` changed between the "before" and "after" commit.
@illicitonion illicitonion merged commit c1521bb into main Oct 4, 2023
2 checks passed
@illicitonion illicitonion deleted the document-relative-bazel-opts branch October 4, 2023 13:34
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