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

Fix common .bazelrc behavior for flag expansions #20720

Closed
wants to merge 1 commit into from

Conversation

fmeum
Copy link
Collaborator

@fmeum fmeum commented Jan 3, 2024

When a flag specified with common in a .bazelrc file expanded to a flag unsupported by the current command, it resulted in an error rather than the flag being ignored.

Fixes #18130 (comment)

When a flag specified with `common` in a `.bazelrc` file expanded to a
flag unsupported by the current command, it resulted in an error rather
than the flag being ignored.
@github-actions github-actions bot added the awaiting-review PR is awaiting review from an assigned reviewer label Jan 3, 2024
@fmeum
Copy link
Collaborator Author

fmeum commented Jan 3, 2024

@justinhorvitz Could you review this?

@fmeum
Copy link
Collaborator Author

fmeum commented Jan 3, 2024

@bazel-io fork 7.1.0

@sgowroji sgowroji added the team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website label Jan 3, 2024
@meteorcloudy meteorcloudy added awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally and removed awaiting-review PR is awaiting review from an assigned reviewer labels Jan 10, 2024
@github-actions github-actions bot removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Jan 10, 2024
bazel-io pushed a commit to bazel-io/bazel that referenced this pull request Jan 10, 2024
When a flag specified with `common` in a `.bazelrc` file expanded to a flag unsupported by the current command, it resulted in an error rather than the flag being ignored.

Fixes bazelbuild#18130 (comment)

Closes bazelbuild#20720.

PiperOrigin-RevId: 597271727
Change-Id: Ieaba4dc00e13495a859e1eedf802759ad7dbf774
@fmeum fmeum deleted the fix-option-expansion branch January 10, 2024 17:37
github-merge-queue bot pushed a commit that referenced this pull request Jan 11, 2024
When a flag specified with `common` in a `.bazelrc` file expanded to a
flag unsupported by the current command, it resulted in an error rather
than the flag being ignored.

Fixes
#18130 (comment)

Closes #20720.

Commit
b303144

PiperOrigin-RevId: 597271727
Change-Id: Ieaba4dc00e13495a859e1eedf802759ad7dbf774

Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
@iancha1992
Copy link
Member

The changes in this PR have been included in Bazel 7.1.0 RC1. Please test out the release candidate and report any issues as soon as possible. If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=last_rc.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants