ux(dashboard): import existing projects by prefixing #5806
Conversation
ghuntley
requested review from
gtsiolis
and removed request for
JanKoehnlein
| @@ -134,7 +134,7 @@ export default class Workspaces extends React.Component<WorkspacesProps, Workspa | |||
| <div className="px-6 py-3 flex justify-between space-x-2 text-gray-400 border-t border-gray-200 dark:border-gray-800 h-96"> | |||
| <div className="flex flex-col items-center w-96 m-auto"> | |||
| <h3 className="text-center pb-3 text-gray-500 dark:text-gray-400">No Active Workspaces</h3> | |||
| <div className="text-center pb-6 text-gray-500">Prefix any git repository URL with gitpod.io/# or create a new workspace for a recently used project. <a className="gp-link" href="https://www.gitpod.io/docs/getting-started/">Learn more</a></div> | |||
| <div className="text-center pb-6 text-gray-500">Import your existing projects by prefixing any git repository URL with gitpod.io/# or create a new workspace for a recently used project. <a className="gp-link" href="https://www.gitpod.io/docs/getting-started/">Learn more</a></div> | |||
There was a problem hiding this comment.
issue: This change could be confusing once we ship Teams & Projects next month[1] as this will not actually import a project but only use the repository as a context. This could get more confusing as we're planning to add workspaces under personal accounts, teams, and projects (see #5555 (comment)). ❗
thought: We could consider having a way to prompt users to add repositories as projects on a team or their personal account while using the prefixed URL before opening the workspace but still this could be available only if they have proper write permissions so this change wouldn't be applicable for everyone.
suggestion: I'd suggest to hold this back this back until we ship Teams & Projects, rephrase it, or close it to avoid any confusion. What do you think?
Cc @svenefftinge because relevant diff.
There was a problem hiding this comment.
yes: importing a project != starting a workspace on a repo
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: No associated issue. Update pull-request body to add a reference to an issue, or get approval with The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Promoting the browser extension within the dashboard sounds great! FWIW, we did have a relevant tips on the loading screen[1][2] before the dashboard redesign, back in March, which we could consider adding back. 🔖 Besides the loading screen, a one-time dismissible notification within the dashboard could be useful. This could be added using a) a toast notification (see #3530), b) a different in-product notification (see relevant discussion (internal) cc @JohannesLandgraf), or c) an updated what's new entry once any upcoming changes to the browser extension are worth adding there.
|
|
This pull request 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. |
|
How shall we proceed? |
|
This pull request 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. |
Description
Watch https://youtu.be/x19DetWAsVA?t=268
@gtsiolis after your thoughts here about plugging the browser extension (and saying folks should install it) in this paragraph as well and explaining that browser extension is the correct/primary way to utilise Gitpod. Not sure what words to use but let's discuss.
Related Issue(s)
How to test
Release Notes