Reached MAX_CREATION_LIMIT forbids user from creating a repo within an org #4452

Closed
opened 2025-11-02 05:51:15 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @fpiecka on GitHub (Dec 6, 2019).

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

Description

A user which has reached MAX_CREATION_LIMIT cannot create a repository in an organization where (s)he is an owner.

However when user's MAX_CREATION_LIMIT isn't reached, (s)he can create any number of repositories in an organization. These repositories aren't counted toward the user's MAX_CREATION_LIMIT, which I consider correct. I believe there should be no restriction based on user's MAX_CREATION_LIMIT state for organization owned repos.

...

Screenshots

Originally created by @fpiecka on GitHub (Dec 6, 2019). - Gitea version (or commit ref): 1.9.5 - Operating system: Debian 9 - 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 ## Description A user which has reached MAX_CREATION_LIMIT cannot create a repository in an organization where (s)he is an owner. However when user's MAX_CREATION_LIMIT isn't reached, (s)he can create any number of repositories in an organization. These repositories aren't counted toward the user's MAX_CREATION_LIMIT, which I consider correct. I believe there should be no restriction based on user's MAX_CREATION_LIMIT state for organization owned repos. ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/bug label 2025-11-02 05:51:15 -06:00
Author
Owner

@fpiecka commented on GitHub (Dec 11, 2019):

It seems the problem is only with web UI. Repos belonging to organizations can be reated using API even when user's MAX_CREATION_LIMIT is reached.

@fpiecka commented on GitHub (Dec 11, 2019): It seems the problem is only with web UI. Repos belonging to organizations can be reated using API even when user's MAX_CREATION_LIMIT is reached.
Author
Owner

@AndrewBezold commented on GitHub (Jan 10, 2020):

Using the master branch from a few days ago, I hit the same issue through the api (user has reached the maximum limit of repositories), so it's not just a web client issue.

EDIT: Nevermind, orgs have a maximum limit as well, disregard

@AndrewBezold commented on GitHub (Jan 10, 2020): Using the master branch from a few days ago, I hit the same issue through the api (user has reached the maximum limit of repositories), so it's not just a web client issue. EDIT: Nevermind, orgs have a maximum limit as well, disregard
Author
Owner

@stale[bot] commented on GitHub (Mar 11, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 11, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Author
Owner

@fpiecka commented on GitHub (Mar 24, 2020):

The issue is still present, please keep it open (even better, fix it:) ).

@fpiecka commented on GitHub (Mar 24, 2020): The issue is still present, please keep it open (even better, fix it:) ).
Author
Owner

@stale[bot] commented on GitHub (Apr 7, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Apr 7, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#4452