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

chore: revise flags example for clarity #315

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: revise flags example for clarity #315

wants to merge 1 commit into from

Conversation

alexeagle
Copy link
Collaborator

No description provided.

❗❗❗<i>Please note that there is an outstanding [bug](https://github.com/bazelbuild/bazel/issues/13603) concerning `--config` and Starlark flags which will be pointed out later in this README. Once a fix is released, this doc will be updated.</i>

### A. Flags on the command line take precedence over those in bazelrc. ###
### A. Flags on the command line take precedence over those in bazelrc.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sanity check: this remains accurate?

I thought there was some logic to inline --config flags into the command line.

--foo=1 --config=something_that_sets_foo --foo2

would evaluate the bazelrc setting second.

https://bazel.build/run/bazelrc supports what's stated here

Options on the command line always take precedence over those in rc files

Maybe I'm remembering outdated logic?

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.

None yet

2 participants