gitpod-io / gitpod-io/gitpod

Nudge users to continue with the provider they previously used to sign in

Open
#7,087 10 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

aspect: authentication component: dashboard meta: never-stale team: webapp type: feature request user experience
Dominant language
TypeScript
Stars
13.8k
Forks
1.4k
Avg merge
17h 58m
Merged PRs (30d)
5

Description

Problem to solve

Following the design updates in https://github.com/gitpod-io/gitpod/issues/7061, the user can still run into the error[1] we show when they try to continue with a provider they haven't added in /integrations when opening a repository.

Proposal

Following the design updates in https://github.com/gitpod-io/gitpod/issues/7061, let's nudge users to continue with the most recent provider they previously used to create an account.

This can be probably achieved using browser local storage which stores all existing connections with providers in /integrations. Cc @AlexTugarev because of a previous discussion on this topic and https://github.com/gitpod-io/gitpod/issues/4696#issuecomment-874496797.

The footnote below the perimary action button could be always visible or only when selected option is a provider not in the stored list in local storage.

Login with nudge about previously used provider
PreviouslySignedIn

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading issue 7061 and the login flow that handles provider selection, then inspect how /integrations connections are represented and stored in browser local storage. Done means users are nudged toward the most recent provider they used when they select a provider they have not added, matching the linked design.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.