Skip to content
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

Prompt users to create a new team when adding a repository from an non-personal account #7008

Closed
gtsiolis opened this issue Dec 1, 2021 · 4 comments
Labels
component: dashboard feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: feature request New feature or request

Comments

@gtsiolis
Copy link
Contributor

gtsiolis commented Dec 1, 2021

Problem to solve

Currently, when going through /new prompt users to select a team after selecting a repository. We recently removed this prompt when a user is trying to add a repository from the personal account, see #6966.

However, a) creating a team for repositories from personal accounts does not sound helpful and b) users could go through adding a new project when viewing personal account projects which is the default dashboard page in / and /projects as we allow users to switch between personal accounts and orgs for GitHub, groups for GitLab, etc.

This is more relevant as adding a project you collaborate on with others on your personal account is not making it possible to invite other team members or allows others to request access to your personal account. 💡

Proposal

Revert the change in #6966 and prompt users to create a new team when adding a repository from an non-personal account.

@gtsiolis gtsiolis added type: feature request New feature or request component: dashboard feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. team: webapp Issue belongs to the WebApp team labels Dec 1, 2021
@stale
Copy link

stale bot commented Mar 2, 2022

This issue 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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Mar 2, 2022
@stale stale bot closed this as completed Mar 13, 2022
@stale stale bot moved this to Done in 🍎 WebApp Team Mar 13, 2022
@gtsiolis
Copy link
Contributor Author

Reopening as this could be interesting to explore.

@gtsiolis gtsiolis reopened this Mar 14, 2022
Repository owner moved this from Done to In Progress in 🍎 WebApp Team Mar 14, 2022
@gtsiolis gtsiolis added the meta: never-stale This issue can never become stale label Mar 14, 2022
@stale stale bot removed meta: stale This issue/PR is stale and will be closed soon labels Mar 14, 2022
@jldec jldec removed the status in 🍎 WebApp Team Mar 28, 2022
@jldec
Copy link
Contributor

jldec commented Mar 28, 2022

(removed in-progress status)

@gtsiolis
Copy link
Contributor Author

Closing this as it will no longer be relevant after the changes in WEB-218.

@github-project-automation github-project-automation bot moved this to In Validation in 🍎 WebApp Team May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: dashboard feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: feature request New feature or request
Projects
Status: In Validation
Development

No branches or pull requests

2 participants