-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Reached MAX_CREATION_LIMIT forbids user from creating a repo within an org #9269
Comments
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. |
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 |
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. |
The issue is still present, please keep it open (even better, fix it:) ). |
This issue has been automatically closed because of inactivity. You can re-open it if needed. |
… repos (#11183) * Fix creation of Org repos Fix #9269 * Change variable name to appease linter * Update PR with suggestions Add a note for user.CanCreateRepo() about failure assumptions Change repo.create help message Co-authored-by: guillep2k <[email protected]>
… repos (go-gitea#11183) * Fix creation of Org repos Fix go-gitea#9269 * Change variable name to appease linter * Update PR with suggestions Add a note for user.CanCreateRepo() about failure assumptions Change repo.create help message Co-authored-by: guillep2k <[email protected]>
[x]
):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
The text was updated successfully, but these errors were encountered: