tree 5d4d89bb57df04935f10c527aff9dd6d48876178
parent 54d1702832d3815e2335612582db7cf463a4d216
author Richard Levasseur <rlevasseur@google.com> 1697573854 -0700
committer GitHub <noreply@github.com> 1697573854 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlLuvvCRBK7hj4Ov3rIwAA4icIABxY7BusL8/vRwsM93ZcUNdy
 kIwwUv1cUVSwEIGrkpM189zzEVAxroYvOqAQ2nosZ/wg6uaVKYSSUxiR2KdIVzcu
 9wtaQIAf/zz94k87pLEc2U7Nnx45uDHPN0qUnvS3MoTBZooA8eg/SQPZDY80Lpcj
 lcpg435zqb7CuliXisJ7qGOCJjWVpz8u/GSEPzxcq/5GMFHnQuP6FvxzoaFp4e1g
 5FpZzJ1FhgYDq4MVDGuYMOUyeTgHxbS5n/DACfZzMC3VWDKSXczmZptNt+x8vK8e
 aopXQagGhYzk3ADeRdbzCRpFWR2HWjGtqjWCtGF5kF0jXZ6jUao7/8YsgXUUX0Y=
 =WwBZ
 -----END PGP SIGNATURE-----
 

docs: initial doc generation using Sphinx (#1489)

This lays the groundwork for using Sphinx to generate user-facing
documentation and
having it published on readthedocs. It integrates with Bazel Stardoc to
generate
MyST-flavored Markdown that Sphinx can process.

There are 4 basic pieces that are glued together:
1. `sphinx_docs`: This rule invokes Sphinx to generate e.g. html, latex,
etc
2. `sphinx_stardoc`: This rule invokes Stardoc to generate MyST-flavored
Markdown
     that Sphinx can process
3. `sphinx_build_binary`: This rule defines the Sphinx executable with
any necessary
dependencies (e.g. Sphinx extensions, like MyST) to process the docs in
(1)
4. `readthedocs_install`: This rule does the necessary steps to build
the docs and
put them into the location the readthedocs build process expects. This
is basically
just `cp -r`, but its cleaner to hide it behind a `bazel run` command
than have
     to put various shell in the readthedocs yaml config.

* Bump Bazel 6 requirement: 6.0.0 -> 6.20. This is necessary to support
  bzlmod and Stardoc.

Work towards #1332, #1484