-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Improve user experience by overcoming the common issues/questions/struggles #10701
Comments
Some related issues, can you link/add to your description, @axonasif ?
|
I think one idea here is to think how we can address them in product by using diagnostics/quick fixes/notifications and other IDE means. Or at least using these IDE means to bring a user attention to such thing and set them on right track by navigating to useful docs. |
Done @loujaybee 👍 |
Thanks @axonasif ! A couple more...
|
New entry added:
|
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. |
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. |
1 similar comment
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. |
Is your feature request related to a problem? Please describe
From my personal experience, here's what I've seen being asked the most on our Discord server and other communication channels such as github, frontapp regarding the SaaS Gitpod.io. Trying to braindump all the important points I can think of now.
.gitpod.yml
tasks
(assuminginit
task and prebuilds is enabled)for each of my workspaces
template-*
repos andworkspace-images
needs more maintenance. (Related: slack thread)Describe the behaviour you'd like
We can try to eliminate the causes for most of the questions and also document the missing parts.
Describe alternatives you've considered
Additional context
cc @akosyakov @loujaybee
The text was updated successfully, but these errors were encountered: