[ENH] Add a separate documentation for pytorch-forecasting v1 and v2#2279
Draft
phoeenniixx wants to merge 1 commit into
Draft
[ENH] Add a separate documentation for pytorch-forecasting v1 and v2#2279phoeenniixx wants to merge 1 commit into
pytorch-forecasting v1 and v2#2279phoeenniixx wants to merge 1 commit into
Conversation
|
One possibility: use gh-pages and dump documentation to specific directories for each version. Example: There is a html at index that redirects to the latest version. You can then add a custom domain. |
Member
Author
|
Thanks a lot for sharing this! I will look into it |
|
There's a CI that dumps the doc files when there's a release. You can also manually edit gh-pages branch. |
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.
Reference Issues/PRs
Fixes parts of #2277 (separation of v1 and v2)
What does this implement/fix? Explain your changes.
This PR create separate header for v2 documentation and creates clear distinction between both the versions and adds clearer api references
checklist for this PR
metricsare still the same as v1modelstable automated and add new models which are not present. Waiting for [ENH] auto-generate model overview table from registry tags #2236 to complete