-
Notifications
You must be signed in to change notification settings - Fork 13
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 in product changelog #7
Conversation
@jeanp413 It's a TODO 🙈, do you have any suggested markdown CSS? |
lets's try first using the same css as vscode release notes an then we can iterate from there if necessary, check |
Nice 👌, not sure about the image because it takes too much screen space but other than that it looks really good |
@loujaybee @akosyakov thoughs about the image, should we keep it or not? |
I think updates to the content should be done directly in Changelog. I would like to see list of highlights and call out to use latest versions in each changelog at the top. Images should go to specific highlights below. cc @Cahllagerfeld @mikenikles |
Not sure what you mean, are you referring to the
We are using the same markdown, if you mean to change the markdown template/format then that should be a different issue in the website repo as it will also affect it |
No i mean decisions about the actual content, not format, i.e. what to put at the top. |
We should use https://code.visualstudio.com/api/advanced-topics/remote-extensions#sync-user-global-state-between-machines to ensure that a user don’t see already seen changelog across different machines (local and Gitpod workspaces) Example |
36a429d
to
5ffa497
Compare
@@ -0,0 +1,318 @@ | |||
/*--------------------------------------------------------------------------------------------- |
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.
maybe we should consider to extract a package and publish it to npm to share between VS Code Browser and Desktop? It can be done separately. But please file a tech-debt issue on gitpod-io.
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.
filed gitpod-io/gitpod#11494
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.
that would be gitpod-shared
@mustard-mh we need to implement a basic caching here using the cache-header value, as the extension runs in node not the browser, you can use storage APi and store the timestap of the last fetch call |
Description
TODO
latest publish date
andmarkdown content
Related Issue(s)
Fixes gitpod-io/gitpod#7537
How to test
F5
Gitpod: Show Release Note
Release Notes
Documentation
Incase you don't want to run it