Limit maximum count of private or public repositories for individual users #1612

Open
opened 2025-11-02 04:06:34 -06:00 by GiteaMirror · 8 comments
Owner

Originally created by @Adrian-Voelker on GitHub (Mar 9, 2018).

  • Gitea version (or commit ref): 1.4.0+rc1-17-g93f34fd
  • Git version:
  • Operating system: Ubuntu 17.10
  • 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

Hello,

At the moment it is possible to select the maximum count of repositories a user is allowed to create.

Can the admin specify the count for public or private repositories individually? What about managing how many forks, mirrors, etc... ?

If the admin cant do this right now would this be a good feature?

Thank you,

Adrian

Originally created by @Adrian-Voelker on GitHub (Mar 9, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.4.0+rc1-17-g93f34fd - Git version: - Operating system: Ubuntu 17.10 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description Hello, At the moment it is possible to select the maximum count of repositories a user is allowed to create. Can the admin specify the count for public or private repositories individually? What about managing how many forks, mirrors, etc... ? If the admin cant do this right now would this be a good feature? Thank you, Adrian
GiteaMirror added the type/featureissue/confirmed labels 2025-11-02 04:06:34 -06:00
Author
Owner

@squash commented on GitHub (Jun 6, 2018):

This would be an important feature for hosted service providers.

@squash commented on GitHub (Jun 6, 2018): This would be an important feature for hosted service providers.
Author
Owner

@axifive commented on GitHub (Jun 6, 2018):

It was discussed here

@axifive commented on GitHub (Jun 6, 2018): It was discussed [here](https://github.com/go-gitea/gitea/issues/1029)
Author
Owner

@squash commented on GitHub (Sep 19, 2018):

While technically it was discussed there, I don't think it's fair to say it was given proper attention. The scope of the discussion was very specific, getting gitea self-hosted, and it was determined to not be a requirement for that purpose, and the discussion ended with that. And here we are, months later, and no additional discussion has happened.

@squash commented on GitHub (Sep 19, 2018): While technically it was discussed there, I don't think it's fair to say it was given proper attention. The scope of the discussion was very specific, getting gitea self-hosted, and it was determined to not be a requirement for that purpose, and the discussion ended with that. And here we are, months later, and no additional discussion has happened.
Author
Owner

@stale[bot] commented on GitHub (Jan 8, 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 (Jan 8, 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

@squash commented on GitHub (Jan 8, 2019):

This issue is of course still unresolved and the not really discussed in the linked thread. Are we going with WONTFIX or just ignoring it or ?

@squash commented on GitHub (Jan 8, 2019): This issue is of course still unresolved and the not really discussed in the linked thread. Are we going with WONTFIX or just ignoring it or ?
Author
Owner

@adelowo commented on GitHub (Jan 10, 2019):

Hi, @squash This isn't ignored. Neither is a WONTFIX appropriate, it already has the kind/feature label and it's just awaiting a PR which no one has sent in yet :)

@adelowo commented on GitHub (Jan 10, 2019): Hi, @squash This isn't ignored. Neither is a `WONTFIX` appropriate, it already has the `kind/feature` label and it's just awaiting a PR which no one has sent in yet :)
Author
Owner

@stale[bot] commented on GitHub (Mar 11, 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 (Mar 11, 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

@mvdkleijn commented on GitHub (Sep 4, 2020):

I'm taking a stab at this since @kasbah seems busy and I could use this too. 😄 Not too familiar with the Gitea code base so any pointers are welcome at PR #12705

@mvdkleijn commented on GitHub (Sep 4, 2020): I'm taking a stab at this since @kasbah seems busy and I could use this too. :smile: Not too familiar with the Gitea code base so any pointers are welcome at PR #12705
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1612