Include `load` in summaries (#216)

Rules, providers, functions and aspects now have a small `load` statement in their summary.

The label in the `load` statement requires forking tests and golden files for --noenable_bzlmod mode; for brevity and maintainability, we are only interested in the following tests for --noenable_bzlmod:

* multiple_files
* same_level_file
* table_of_contents
* local_repository (this one needs no forking)

---------

Co-authored-by: Alexandre Rostovtsev <arostovtsev@google.com>
57 files changed
tree: 1cf001346a0eda51b2b23b433df0de85759163af
  1. .bazelci/
  2. distro/
  3. docs/
  4. src/
  5. stardoc/
  6. test/
  7. .bazelignore
  8. .bazelrc
  9. .gitignore
  10. AUTHORS
  11. BUILD
  12. CHANGELOG.md
  13. CODEOWNERS
  14. CONTRIBUTING.md
  15. CONTRIBUTORS
  16. deps.bzl
  17. LICENSE
  18. maven_install.json
  19. MODULE.bazel
  20. README.md
  21. rules_jvm_external.patch
  22. setup.bzl
  23. update-release-binary.sh
  24. update-stardoc-docs.sh
  25. update-stardoc-tests.sh
  26. version.bzl
  27. WORKSPACE
  28. WORKSPACE.bzlmod
README.md

Stardoc - Starlark Documentation Generator

Build status

Stardoc is a documentation generator for Bazel build rules written in Starlark.

Stardoc provides a Starlark rule (stardoc, see documentation) that can be used to build documentation for Starlark rules in Markdown. Stardoc generates one documentation page per .bzlfile.

Get Started

About Stardoc

Project Status

Skydoc deprecation

Stardoc is a replacement for the deprecated “Skydoc” documentation generator.

See Skydoc Deprecation for details on the deprecation and migration details.

Future plans

See our future plans for refactoring Stardoc to be more consistent with how Bazel evaluates .bzl files, and what it means for maintenance of this project.

Maintainer's guide

See the maintaner's guide for instructions for cutting a new release.