Fix root-level 404 handling in multiversion Sphinx docs deployment#149
Open
AlgoFoe wants to merge 1 commit intoneuroinformatics-unit:mainfrom
Open
Fix root-level 404 handling in multiversion Sphinx docs deployment#149AlgoFoe wants to merge 1 commit intoneuroinformatics-unit:mainfrom
AlgoFoe wants to merge 1 commit intoneuroinformatics-unit:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
What is this PR
Why is this PR needed?
404.htmlfrom the root of thegh-pagesbranch. While each documentation version correctly generates its own404.html, the root-level file was not being updated during deployment.What does this PR do?
deploy_sphinx_docs_multiversionaction to copy the built version’s404.htmlfile to the root of thegh-pagesbranch during deployment.References
How has this PR been tested?
404.htmlexists.Is this a breaking change?
Does this PR require an update to the documentation?
Checklist: