Allow a team access to all repositories #1877

Closed
opened 2025-11-02 04:16:16 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @mrichar1 on GitHub (Jun 6, 2018).

  • Gitea version (or commit ref):fa3ceb6
  • Git version: 1.8.3.1
  • Operating system: try.gitea.io
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Is there a way in which a team can be set up such that it automatically has write access over all repos, including ones yet-to-be-created?

Alternatively, can there be a way to bulk-add repos to the team rather than having to add them through the auto-complete form? And/or have a way to add teams to a repo, similar to the Collaboration tab in the repo settings?

Originally created by @mrichar1 on GitHub (Jun 6, 2018). - Gitea version (or commit ref):fa3ceb6 - Git version: 1.8.3.1 - Operating system: try.gitea.io - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description Is there a way in which a team can be set up such that it automatically has write access over all repos, including ones yet-to-be-created? Alternatively, can there be a way to bulk-add repos to the team rather than having to add them through the auto-complete form? And/or have a way to add teams to a repo, similar to the `Collaboration` tab in the repo settings?
GiteaMirror added the type/feature label 2025-11-02 04:16:16 -06:00
Author
Owner

@lunny commented on GitHub (Dec 8, 2018):

We could add an option on team settings to automatically add repository and for an owner it's default true and other team default false to keep compatible with old version.

@lunny commented on GitHub (Dec 8, 2018): We could add an option on team settings to automatically add repository and for an owner it's default true and other team default false to keep compatible with old version.
Author
Owner

@stale[bot] commented on GitHub (Feb 6, 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[bot] commented on GitHub (Feb 6, 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.
Author
Owner

@lunny commented on GitHub (Feb 7, 2019):

duplicated with #3642

@lunny commented on GitHub (Feb 7, 2019): duplicated with #3642
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1877