-
Notifications
You must be signed in to change notification settings - Fork 120
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
Add version support to published docs #358
Comments
That sounds like a good idea. If someone can come up with a not too complicated setup for this, it would be greatly appreciated :) In the mean time, maybe we should only update github pages when we push a new release, not for every commit on main @dbrgn ? |
Yeah, it would probably make sense to have versioned docs. I don't know what would be required for that though. |
That might be a good stop-gap solution until then. |
Hi,
Can versioning be added to the docs? I'm a new user and went through a fair amount of unnecessary steps to figure out custom page extension listed in docs is for an unreleased commit in main. :(
Extension changed: #320
No
.md
extension docs for 1.6.1 tag: https://github.com/dbrgn/tealdeer/blob/v1.6.1/docs/src/usage_custom_pages.mdWith
.md
extension live docs with new extension: https://dbrgn.github.io/tealdeer/usage_custom_pages.htmlThanks for the client!
The text was updated successfully, but these errors were encountered: