Most rulesets don't provide a lot of value based on the one-liner snippet we offer for copy-pasting via the UI (e.g. all that involve package manager usage).
Right now there is no clear way about how we could include that, without including it as a metadata field in the BCR (which is undesirable for multiple reasons.
What we could do is adding a link to the repository (and their release notes, where the snippet is most often found) based on the repository key in the metadata.json.
Most rulesets don't provide a lot of value based on the one-liner snippet we offer for copy-pasting via the UI (e.g. all that involve package manager usage).
Example of more involved copy-pastable boilerplate: https://github.com/bazelbuild/rules_python/releases/tag/0.15.0
Right now there is no clear way about how we could include that, without including it as a metadata field in the BCR (which is undesirable for multiple reasons. What we could do is adding a link to the repository (and their release notes, where the snippet is most often found) based on the
repositorykey in themetadata.json.