eldritch horrors
d9bc197ff4
not sure why this was done the way it was considering that includes are a feature the doc toolchain had previously. let's just always have some kind of entry for the upcoming release in the dev manual builds even if that means having a completely empty release notes chapter. the release notes generation script isn't entirely functional right now due to pre-commit hooks, but it's good enough for time being. we need a better release process for notes anyway. Change-Id: |
||
---|---|---|
.. | ||
rl-next | ||
rl-next-dev | ||
src | ||
theme | ||
anchors.jq | ||
book.toml | ||
custom.css | ||
docroot.py | ||
generate-builtin-constants.nix | ||
generate-builtins.nix | ||
generate-manpage.nix | ||
generate-manpage.py | ||
generate-xp-features-shortlist.nix | ||
generate-xp-features.nix | ||
local.mk | ||
meson.build | ||
process-includes.sh | ||
quote-literals.xsl | ||
redirects.js | ||
render-manpage.sh | ||
utils.nix |