-
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
Allow using deleted team name #6211
Comments
Thanks for opening this @jankeromnes! For the first point, see #5066 (comment). Cc @laushinka @svenefftinge For the second point, see #4623. |
/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. |
@jankeromnes Thanks for this issue! Yes, the first point makes sense. Re the second point, it seems that there are more solution options as @gtsiolis linked. Should it be tackled in that issue instead (and have it updated in case of staleness)? |
/assign |
@laushinka I have scheduled #4623 since there was already some work done there on the last-member deletion UX. cc: @gtsiolis |
Currently, in the context of the new Teams & Projects UI, there are two problems related to the deletion of a Team:
To fix this, the TeamsDB should ignore all teams that have
markedDeleted: true
when looking at existing teams / existing team slugs / etc (the same way as it currently ignores all teams that havedeleted: true
):gitpod/components/gitpod-db/src/typeorm/team-db-impl.ts
Lines 126 to 129 in 6bf6485
Note: This also applies to all locations in TeamsDB where
deleted: false
is required.- [ ] When you are the last person to leave a Team, the team ends up having 0 members (hence no longer being accessible to anyone)Issue exists in #4623In this case (when the last person leaves), the Team should also getmarkedDeleted
:gitpod/components/gitpod-db/src/typeorm/team-db-impl.ts
Lines 203 to 204 in 6bf6485
The text was updated successfully, but these errors were encountered: