Tony Aiuto

Another upvote for this, with another motivating use case. Let's say I have a .bzl file defining 2 rules (`a_impl`, `b_impl`) and their 2 wrappers (`a`, `b`), and I try...

FWIW I hacked up something like this in rules_pkg earlier this year. I do a stardoc for each .bzl file that needs it, then post-process that to merge into a...

Adding to the feature request. We want to pull up docstrings from the wrapped rule to the description. But we also want to be able to override the docstring from...

> See also: [bazelbuild/bazel#22403](https://github.com/bazelbuild/bazel/issues/22403), which asks for a way of attaching license info to a specific target (which we will need for `rules_jvm_external`) Does `rules_jvm_external` combine multiple distinct modules into...

I want to hold off on this for a minute. I have a lot of enhancements to this which we developed during Google's EO compliance sprint that I want to...

I don't agree. We have been moving towards having both the core rules and the baseline set of tools in this same repository. That will require distinct MODULE.bazel files for...

Can you put a high level overview of the intent in the PR description. It seems this is on the right track, but it's hard to say without a clear...

I like the general idea, but I think we should tweak it a bit and not do it early, but rather do it at SBOM generation time. That is, -...

I'm not sure if this is a bug report or just highlighting a different problem. gather_licenses_info should capture all `license_info()` and `package_info()` instances in BUILD files from external repositories. So...

Hi Bill. I just wanted to run this idea by you. It's not urgent. I want to hear what users say at BazelCon