bazelbuild / bazelbuild/rules_license

The rules to declare licenses and their kinds should be in a distinct bazel package from the ones that consume them.

Open
#85 1 comment 0 reactions 1 assignee Claimed by @aiuto View on GitHub
internal_cleanup P2
Dominant language
Starlark
Stars
85
Forks
37
PR merge metrics
No merged PRs in 30d

Description

There are too many things in the `rules` package.
The expected use case is that everyone is going to by declaring a `license` rule, but fewer people will be using those to produce license audit or SBOMs. Most of the people who do produce an SBOM are expected to check rules_license into their repo and modify or reuse as appropriate, so having a clear separation between the packages you modify and the ones you leave alone is helpful.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.