Skip to content

Project Configuration: No indication when or where config file was saved #6724

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

Closed
jldec opened this issue Nov 16, 2021 · 9 comments
Closed
Labels
component: dashboard feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. meta: stale This issue/PR is stale and will be closed soon team: webapp Issue belongs to the WebApp team user experience

Comments

@jldec
Copy link
Contributor

jldec commented Nov 16, 2021

Users have a hard time forming a picture of what is happening to the config shown in the Project Configuration page. It would be really helpful to have a indication which tells users what the state is. Suggestions below:

  • Suggested configuration, will be saved in Gitpod and included as uncommitted file in workspace.
  • Saved in Gitpod, suggest committing to repository.
  • Saved in repository.
@jldec jldec added team: webapp Issue belongs to the WebApp team user experience feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. labels Nov 16, 2021
@jldec
Copy link
Contributor Author

jldec commented Nov 16, 2021

Depends on #5522 if we promise that we're going to add the config file to your workspace.

@jldec
Copy link
Contributor Author

jldec commented Nov 16, 2021

See also #slack (internal)

@jldec jldec moved this to In Groundwork in 🍎 WebApp Team Nov 16, 2021
@jldec
Copy link
Contributor Author

jldec commented Nov 24, 2021

/schedule
/assign @AlexTugarev

Given that you are working on #5785
This would leave only 2 states to worry about to explain with a message to the user

  1. The configuration above will be used for the first prebuild or other start tasks, and included as an uncommited file in the workspace. Committing the file to your repository will allow Gitpod to use it for future workspaces.

  2. This repository has a .gitpod.yml configuration file. (edited)

@roboquat
Copy link
Contributor

@jldec: Issue scheduled in the meta team (WIP: 0)

In response to this:

/schedule
/assign @AlexTugarev

Given that you are working on #5785
This would leave only 2 states to worry about to explain with a message to the user

  1. The configuration above will be used for the first prebuild or other start tasks, and included as an uncommited file in the workspace. Committing the file to your repository will allow Gitpod to use it for future workspaces.

  2. This repository has a .gitpod.yml configuration file. (edited)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@AlexTugarev
Copy link
Member

@jldec, I think this can be closed now, right? It's no longer relevant, if we remove the config page.

@jldec
Copy link
Contributor Author

jldec commented Dec 8, 2021

Let's keep it to help those users who use the config page from the project dashboard.

@jldec
Copy link
Contributor Author

jldec commented Dec 8, 2021

/unschedule

@jankeromnes
Copy link
Contributor

I think we can close this page, as the Project Configuration page has been moved out of the onboarding flow, and will soon be removed entirely, because the Project Configuration feature itself is now deprecated in favour of the auto-generated .gitpod.yml that is now added to every unconfigured workspace.

@stale
Copy link

stale bot commented Apr 8, 2022

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Apr 8, 2022
@stale stale bot closed this as completed Apr 19, 2022
@stale stale bot moved this to Done in 🍎 WebApp Team Apr 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: dashboard feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. meta: stale This issue/PR is stale and will be closed soon team: webapp Issue belongs to the WebApp team user experience
Projects
Archived in project
Development

No branches or pull requests

5 participants