ci: use mdbook_server and dynamic path for docs build

- Add mdbook_server target to //docs:serve for easier local development.
- Update github_pages.yml to dynamically determine the documentation
  output path using bazel cquery.

Signed-off-by: Miguel Osorio <miguelosorio@google.com>
2 files changed
tree: 36ed09a4374ab8ae05fdd30008872ea66ac1d2ae
  1. .cargo/
  2. .github/
  3. docs/
  4. hal/
  5. openprot/
  6. platform/
  7. presubmit/
  8. services/
  9. third_party/
  10. xtask/
  11. .bazelignore
  12. .bazelrc
  13. .bazelversion
  14. .clang-format
  15. .gitignore
  16. .semgrepignore
  17. BUILD.bazel
  18. Cargo.lock
  19. Cargo.toml
  20. deny.toml
  21. LICENSE
  22. MODULE.bazel
  23. MODULE.bazel.lock
  24. pw
  25. README.md
  26. rust-toolchain.toml
  27. workflows.json
README.md

OpenPRoT

Technical Charter

The OpenPRoT Technical Charter can be found at https://github.com/OpenPRoT/.github/blob/main/GOVERNANCE.md

Getting Started

NOTE: We are converting our build system to bazel. We recommend installing bazelisk to automatically manage bazel versions.

Available Tasks

You can run tasks using the Pigweed workflow launcher pw or bazel.

  • ./pw presubmit - Run presubmit checks: formatting, license checks, C/C++ header checks and clippy.
  • ./pw format - Run the code formatters.
  • bazel test //... - Run all tests.
  • bazel build //docs - Build documentation.

Development

The project is structured as a bazel module.

Requirements

  • Bazel. We recommend installing bazelisk to automatically manage bazel versions.

No additional tools are required - all dependencies are managed by bazel.