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.

Sign up for GitHub

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

Jump to bottom

Flip default for --incompatible_enforce_config_setting_visibility #39

Open
alexeagle opened this issue Mar 22, 2022 · 1 comment
Open

Flip default for --incompatible_enforce_config_setting_visibility #39

alexeagle opened this issue Mar 22, 2022 · 1 comment
Labels
bazel-flags Flip default for Bazel flags bounty-1000USD A contributor who completes this will be rewarded $1000

Comments

@alexeagle
Copy link
Contributor

Help to finish bazelbuild/bazel#12932 by finding Bazel CI projects which need the flag explicitly turned off, then land a PR in Bazel to change the default value for new projects.
@alexeagle alexeagle added the bounty-1000USD A contributor who completes this will be rewarded $1000 label Apr 20, 2022
@cgrindel cgrindel added the bazel-flags Flip default for Bazel flags label Aug 9, 2022
@cgrindel cgrindel moved this to Needs Implementation in Rules SIG Tracker Aug 9, 2022
@cpsauer
Copy link

cpsauer commented May 11, 2023

Heads for anyone else reading this list, editing their .bazelrc that
--incompatible_enforce_config_setting_visibility has already been flipped and it's
--incompatible_config_setting_private_default_visibility that remains here, with keertk working to change.

(If someone with editing power reads this and wants to, maybe we should change the title and text to reduce confusion.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bazel-flags Flip default for Bazel flags bounty-1000USD A contributor who completes this will be rewarded $1000
Projects
Rules SIG Tracker
Status: Needs Assignment
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alexeagle @cgrindel @cpsauer