CI: Build docs in CI #498
CI: Build docs in CI #498
Conversation
erlend-aasland
force-pushed
the
ci/docs
branch
2 times, most recently
from
96bb243 to
9bcb219
Compare
|
Our "CI" for the docs actually lives on readthedocs.org, as each commit on This doesn't make an effort though to separate action runs between docs-only and code-only changes, as mentioned in #497? Since any code change also affects the docs, and docs-only fixes are rare, I can live with that. |
Yes. I'm not used to the docstrings being so tightly coupled with the rendered docs; I simply forgot that it's not possible to do that separation with the current setup. |
|
I just hope Someone(TM) will be there to bump these versioned dependencies when they have bit-rotted enough ;-) Let's try what happens with this action. |
|
So it seems there are no artifacts? Wouldn't it make sense to build some kind of HTML bundle while we're already generating the docs? |
That's a very good idea. |
Also: - bump GitHub checkout action to v4 - bump GitHub setup-python action to v5 - ignore README and LICENSE files - invoke pip according to best practise Follow-up of christiansandberg#498
Also: - bump GitHub checkout action to v4 - bump GitHub setup-python action to v5 - ignore README and LICENSE files - invoke pip according to best practise Follow-up of christiansandberg#498
Also: - bump GitHub checkout action to v4 - bump GitHub setup-python action to v5 - ignore README and LICENSE files - invoke pip according to best practise Follow-up of #498
Resolves #497