-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Customise onboarding (Customise when: Gitpod release and Gitpod Walkthrough are shown) #12704
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
Comments
Also, worth noting that: Currently it shows release notes for every new workspace (it should be limited to the first workspace only, after every release) Related Internal Discussion |
This is a bug, not expected behaviour let's raise a separate issue 🙏 |
Opened a new issue here: #13638 |
The options for disabling release notes altogether are here 🙂: both in VS Code Browser and VS Code Desktop. The configuration is |
Closing this, as @filiptronicek mentioned now there's |
Thanks @jeanp413 ! I will improve the description of this issue. It's useful to know that release notes can be configured! I don't believe that's covered in our documentation, is it? If not it should be! This issue was more about re-thinking the different user contexts of our onboarding. We are currently assuming that all users want to see the changelog and gitpod onboarding walkthrough, but for our customers, or in an open source context, having customizable onboarding flows makes a lot of sense. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
With changelogs gone from our VS Code distributions, is it time to close this @loujaybee? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Context
There are some cases where users might not want the changelog (for Open Source, and Self-Hosted, etc).
Use Cases
Potential solutions
The text was updated successfully, but these errors were encountered: