Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_license/b95957eca8b2fb7bd470ee22440d971c983f536f
commit
b95957eca8b2fb7bd470ee22440d971c983f536f
[log]
author
Tony Aiuto <tony.aiuto@datadoghq.com>
Thu Oct 23 09:37:36 2025 -0400
committer
GitHub <noreply@github.com>
Thu Oct 23 09:37:36 2025 -0400
tree
5ee6595a93d6dc65b1bd4558ee3d8b48bee41b03
parent
3143f521ecaf0b80edf1f1f319c3256bcdae3c9d [diff]
parent
a0de7c431335bd70c03ce22022b4a81c48784d99 [diff]
Add explicit load of cc_library rules in tests

Add explicit load of cc_library rules in tests
This fixes CI at bazel last_green
tree: 5ee6595a93d6dc65b1bd4558ee3d8b48bee41b03
  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

:warning: WARNING
Active development has moved to https://github.com/bazel-contrib/supply-chain. Please look there for current status. If you wish to contribute, please consider doing your work there.

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 license declarations into artifacts to ship with code
  • applying organization specific compliance constraints against the set of packages used by a target.
  • producing SBOMs for built artifacts.

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.