Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_license/fd5464135dffe2728624c6cf3792e3ee1ee9b33e
commit
fd5464135dffe2728624c6cf3792e3ee1ee9b33e
[log]
author
Tony Aiuto <aiuto@google.com>
Thu Jun 08 12:24:11 2023 -0400
committer
Tony Aiuto <aiuto@google.com>
Thu Jun 08 12:24:11 2023 -0400
tree
7f4c0b6397908dc28df4ff739916a61fe39c9b3f
parent
e7274050df8f119b750a792ef669d4d52e2aa572 [diff]
Move rules/private/gathering_providers.bzl to rules_gathering/gathering_providers.bzl

- They should not have been in basic rules/...
- buildifier keeps complaining about accesing things from private (ain't
  no 'friends' class in bazel)
- Leave a temporary forwarder
11 files changed
tree: 7f4c0b6397908dc28df4ff739916a61fe39c9b3f
  1. .bazelci/
  2. .github/
  3. admin/
  4. distro/
  5. doc_build/
  6. docs/
  7. examples/
  8. licenses/
  9. rules/
  10. rules_gathering/
  11. sample_reports/
  12. tests/
  13. tools/
  14. .gitignore
  15. BUILD
  16. CODEOWNERS
  17. deps.bzl
  18. LICENSE
  19. MODULE.bazel
  20. README.md
  21. version.bzl
  22. WORKSPACE
  23. WORKSPACE.bzlmod
README.md

rules_license

CI: Build status

This repository contains a set of rules and tools for

  • declaring metadata about packages, such as
    • the licenses the package is available under
    • the canonical package name and version
    • copyright information
    • ... and more TBD in the future
  • gathering those license declarations into artifacts to ship with code
  • applying organization specific compliance constriants against the set of packages used by a target.
  • (eventually) producing SBOMs for built artifacts.

WARNING: The code here is still in active initial development and will churn a lot.

If you want to follow along:

Background reading: These is for learning about the problem space, and our approach to solutions. Concrete specifications will always appear in checked in code rather than documents.