-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Cannot add a new project when having two accounts #6268
Comments
@gtsiolis, how to render errors on the "Select Git Provider" page of New Project wizard? Do we have some visuals for that? 🙏🏻 |
/schedule |
@JanKoehnlein: Issue scheduled in the meta team (WIP: 0) In response to this:
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. |
/assign @gtsiolis |
Becuase this only impacts a subset of users, this is lower priority cc: @JanKoehnlein |
Nice catch @laushinka! ⚾ Ideally, we would automatically associate these accounts, see #5975. Cc @AlexTugarev because #5975 (comment). 🧙 Following the pattern used in the login page (see #3950), we could re-use it here below the provider selection, see early design specs below using an updated component design.
❗ The risk here is that we can not just prompt users to select a different provider as they are already logged in. Possible copy we could use here for the alert title:
@AlexTugarev what do you think? |
@laushinka and @gtsiolis, in such a case rendering of a useful message is a great idea. |
Bug description
When trying to add a new GitLab project under gitpod.io/new, I could not move forward and received no error messages. Supposedly this is caused by having two Gitpod accounts.
https://www.loom.com/share/ba9d0b291d1e491baafe7a1bd7db9ed3
Steps to reproduce
As the above video:
Workspace affected
No response
Expected behavior
I expect to be able to add a project, or see a helpful error message.
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: