Alex Eagle

Sorry, no I don't see any settings I can change for this. Note that each individual member can choose whether they'd like their membership to be public-visible: https://docs.github.com/en/organizations/organizing-members-into-teams/changing-team-visibility Maybe @meteorcloudy...

@opicaud @zhangskz I think this can be closed?

Yes I have some clients who needed to patch around rules_python. Also Aspect's rules_py uses `all_whl_requirements` to be able to create its virtualenv https://github.com/search?q=repo%3Aaspect-build%2Frules_py%20all_whl_requirements&type=code Could you avoid a breaking change?

Note, I discussed this a bit with @gregmagolan since this is exactly the same shape as the copy_to_directory Go toolchain we build and publish with https://github.com/aspect-build/bazel-lib - we could probably...

It also doesn't make sense to print that warning for `bazel run` since we don't care whether it was a build output or a source file. For example running `bazel...

I agree, that's a nice formulation that avoids touching the existing release procedure for the protobuf module and allows OSS maintainers to own this setup without google3 access. I think...

Ooh, did you find that documented? If not I would like to re-open this to track the missing docs

Ah, I just ran across this as well downstream in bazel-lib where we have the `tar` rule, filed https://github.com/bazel-contrib/bazel-lib/issues/1018

@fmeum said on the linked slack thread > bsdtar seems to contain locale-sensitive logic and it's possible that this be removed during its build (say as a configure option). Since...

Note, https://gitlab.arm.com/bazel/toolchain_utils/-/commit/fc7d485887292676b5a87eb51c40f92aa6343b6b shows one approach for fixing this. `--incompatible_use_plus_in_repo_names` was released in 7.3.0rc1, we should start testing all our repos with this.