Doc build #166
Merged
Doc build #166
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
- Refactored the documentation workflow and deploy process to use the latest version of Mike for better control and flexibility. - Added separate steps to build and deploy legacy and latest documentation versions. - Set the latest version as the default version for the documentation.
Merge from main into doc_build
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.
What does this PR do?
Where should the reviewer start?
Ensure all tests are passing and that the documentation website is deployed correctly. When deployed it will contain the 'latest' and 'archived' versions of the doc website.
How should this PR be tested?
Any background context you want to provide?
The source code (tutorials and tests) should be checked before merging. Some parts of the documentation may contain broken links (because of the tpot2 to tpot renaming.) But these visual elements will be fixed after migrating all source code to the original tpot repo.
Questions:
Do the docs need to be updated?
Does this PR add new (Python) dependencies?