No more pre-building by-default, switching to recursive builds #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
❌ stalled until branches can be selected via
conf.py
The package, currently, first prebuilds all branches and tags via vanilla sphinx in an isolated location and then builds all the specified branches/tags via the
sphinx-versioned-docs
extension.This may work for small projects, however, as the number of branches increases along with the project size, a more reasonable approach will be to build all branches with
sphinx-versioned-docs
and if any fails then initiate the building workflow for all branches except the failed ones.This recursive approach will improve build times.
Branches to be ignored can be specified via
--branch
arg as mentioned in #69(If any branch build fails then the building workflow is re-initated for all branches except the failed one. Pre-building can still be enabled via
--prebuild
cli arg.)