Fast doc build

[Pyrsos]

Sorry, made a mess on this with the branches. Here are the latest changes for building the docs fast issue #4435
Again apologies for the mess...

Depending on what your PR does, here are a few things you might want to address in the description:

• what are the (breaking) changes that this PR makes?
• important background, or details about the implementation
• are the changes—especially new features—covered by tests and docstrings?
• linting/style checks have been run
• consider adding/updating relevant example notebooks
• right before it's ready to merge, mention the PR in the RELEASE-NOTES.md

[OriolAbril]

Looks good, I would name the file fast_build_docs.sh though, as this one does not deploy them to github pages (and should not)

[MarcoGorelli]

Thanks @Pyrsos , much faster like this!

Have just left one small comment, other than that it looks good to me

[MarcoGorelli]

As an aside, maybe there should be another script build_docs.sh which:

• fetches the latest changes from the main branch in pymc-examples (git submodule update --remote)
• builds the full docs without deploying them

Even better if they could be Python scripts instead of bash ones, so that any contributor on any OS can easily build the docs with just one script

Anyway, all this could be a separate PR

---

Last piece of advice here would be to make PRs from new branches rather than from master

[Pyrsos]

Sorry for the delay @MarcoGorelli, I have now made the suggested changes. I'd be happy to work on a separate PR for your suggestions to change from bash scripts to Python scripts. Should I open an issue for this?

[MarcoGorelli]

cool, thanks!

and yes, I think opening an issue would be good so it doesn't get forgotten

[Pyrsos]

OK, I have opened another issue here #4483. Is there anything else I need to do with this one or can it be merged? I do not think I have write access to the repository to do the merge.

[OriolAbril]

This is all for now, the other tasks have issue remainders and can be done in follow up PRs. Thanks for the PR @Pyrsos !