-
-
Notifications
You must be signed in to change notification settings - Fork 479
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
Docs showing unreleased version #764
Comments
Ah, that's a great idea. Will do. |
(This has been reported before in #666, it led to getsentry/sentry-docs#131 being opened) |
OK, the official line is we're going to do more marking of version changed/added of particular features (even/especially when not yet released). |
Shouldn't all unreleased changes be marked as such before closing this? Issue is still present, and others will likely trip over it until properly fixed (I know about it now, I think I will stick to browsing the docs per tag here on GitHub, but just want to help Sentry improve the service for newcomers) |
@dentarg Well, I'm releasing a new version today so that will also fix the issue 😆 |
Haha 👍 |
At the moment there are a few PRs and commits that haven't been released to Rubygems yet. However, the Sentry docs system will show the unreleased docs from master, which could cause confusion.
A way to solve this is to create a branch
latest-release
every time we push to Rubygems, and add the following to sentry-docs/.gitmodules:[submodule "doc-modules/raven-ruby"] path = doc-modules/raven-ruby url = https://github.com/getsentry/raven-ruby + branch = latest-release
The text was updated successfully, but these errors were encountered: