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

I want a team in organization can has all repository,not have to add it one by one #6409

Closed
yashen opened this issue Mar 22, 2019 · 7 comments · Fixed by #8688
Closed

I want a team in organization can has all repository,not have to add it one by one #6409

yashen opened this issue Mar 22, 2019 · 7 comments · Fixed by #8688
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality

Comments

@yashen
Copy link

yashen commented Mar 22, 2019

Description

In most of my case,all member has all repositories,just different permissions,
so I want a team in organization can has all repository,not have to add it one by one

@axifive
Copy link
Member

axifive commented Mar 22, 2019

Maybe for this case better add the second button: "Add all repositories"

@lunny
Copy link
Member

lunny commented Mar 22, 2019

@axifive I would like one checkbox to all repositories and don't need to really select all the repositories.

@axifive
Copy link
Member

axifive commented Mar 23, 2019

Screenshot
@lunny, At this moment we have only search field without repositories list. So it seems to me that the checkbox conception doesn’t fit here.

@lunny
Copy link
Member

lunny commented Mar 23, 2019

@axifive When create a team, we can add a checkbox(default false) to enable all repositories or not. Then on this page's repositories, it will display like an Owner team. We only need add a column on team table maybe named is_all_repositories to do that.

@axifive
Copy link
Member

axifive commented Mar 23, 2019

@lunny Ok, I got it now.

@stale
Copy link

stale bot commented May 23, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label May 23, 2019
@techknowlogick techknowlogick added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels May 23, 2019
@rlogiacco
Copy link

I also wish to see this implemented and I can try to give this a shot if anybody points me in the right direction....

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality
Projects
None yet
5 participants