Skip to content

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

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

Open
2 of 7 tasks
Adrian-Voelker opened this issue Mar 9, 2018 · 8 comments
Open
2 of 7 tasks
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@Adrian-Voelker
Copy link

Adrian-Voelker commented 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

@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Mar 10, 2018
@squash
Copy link

squash commented Jun 6, 2018

This would be an important feature for hosted service providers.

@axifive
Copy link
Member

axifive commented Jun 6, 2018

It was discussed here

@squash
Copy link

squash commented 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.

@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Jan 8, 2019
@squash
Copy link

squash commented 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 ?

@stale stale bot removed the issue/stale label Jan 8, 2019
@adelowo
Copy link
Member

adelowo commented 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 :)

@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Mar 11, 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 Mar 11, 2019
@mvdkleijn
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants