-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DRAFT - DO NOT MERGE ⚠️ feat: Reintroduce multiversion docs #2622
base: main
Are you sure you want to change the base?
Conversation
6aacbbd
to
859172d
Compare
Weird - I don't see a "draft" option for this PR, maybe because |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @cicdguy!! Shall I merge this in now?
We have a new CRAN release on Jan 15 be great to work out any kinks before that
Not yet - I'll need to push the past versions into the |
Roger! I guess that is why you wanted to set it to DRAFT! Just ping me if you want a second set of eyes or to merge in. Thanks again for making this update - I know you are in high demand! |
I'll revisit this after the upcoming release. Do not want to disrupt anything that way. |
Reintroduces the multiversion docs feature per @manciniedoardo's request.
The change was reverted in ee3e5b1 per @pharmaverse/admiral's decision.
This PR will reintroduce multiversion docs.
See examples where this is successfully used: