-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[teams] make Gitpod icon team-aware #5854
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
Conversation
/werft run 👍 started the job as gitpod-build-alex-persist-team-selection-on-5519.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @AlexTugarev! Navigation changes work like a charm! 🔮
Couldn't reproduce defaulting to personal account when importing from GitLab.com. 😭
We're still missing persisting team selection when reloading /
as described in #5519 but we could improve that later or in a follow-up issue. ➿
Approving to unblock merging but holding in case we need someone to take a closer look at the code changes.
/hold
@@ -22,6 +22,13 @@ export class GitLabAppSupport { | |||
const api = new Gitlab({ oauthToken }); | |||
|
|||
const result: ProviderRepository[] = []; | |||
const ownersRepos: ProviderRepository[] = []; | |||
|
|||
const identity = params.user.identities.find(i => i.authProviderId === "Public-GitLab"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue: This is related #5331, right? I'm still seeing a different top-level group selected by default when trying to add a new project from GitLab.com. Expected? 😭
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh no, that commit shouldn't go to that branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed
LGTM label has been added. Git tree hash: 59a8935dacf04a1d362aabde5202b373bbf29120
|
c02bd10
to
c267ce3
Compare
New changes are detected. LGTM label has been removed. |
/werft run 👍 started the job as gitpod-build-alex-persist-team-selection-on-5519.4 |
@AlexTugarev let me know if you need another review round for this. 🏓 |
@gtsiolis, yes please! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Flawless! Thanks @AlexTugarev! ⭕
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AlexTugarev, gtsiolis Associated issue: #5519 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
if (team) { | ||
// updating last team selection | ||
try { | ||
localStorage.setItem('team-selection', team.slug); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And how can you revert back to User is selected by default? Current code reads like if you select a team once, you'll forever have a team selected by default, never your own user.
Also, I find restoring this selection on page load quite dangerous, and would personally prefer we rely on URLs for correct team selection (i.e. no local storage + restore on root).
fair point. let me check, but I think unsetting when navigating away from a team's page sounds reasonable.
that's the whole point. if you recently visited a team's page and then open |
Description
Related Issue(s)
Fixes #5519
How to test
Release Notes