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
bug: Non-admins can not create repos for organizations #16575
Comments
A discussion about this was started here #15924 (comment), but we had no concluding decision. It's unclear what the best behaviour for this is, but I agree that it can be confusing. A quick proposal: introduce a new instance-wide or per-user setting
Gitea has enough config options already, so there should be enough people wanting this feature to justify adding this complexity.. |
I think this is unnecessarily complicated. In contrast, I would propose not using the limit of the organization to check whether a repository may be created, but the limit of the user creating the repository at this moment. This is basically possible already by creating the repo in your own user namespace and then transfering it to the organization. |
@MGChecker this is how it works currently. One of us is misunderstanding something here, not sure who 😅 |
I agree that this is how it should work, but it does not in my setup. Even though the user repository limit is larger than 0, they may still not create a repository inside the organization. The form is shown, but on submit the error message mentioned above is shown. |
I think this is a misunderstanding and this is actually a bug. |
If a non-admin tries to create a repository inside an organization they own, they get an error their repository limit would be reached. In my configuration the default repository limit for users is 0.
Specifically, the following error is shown:
form.reach_limit_of_creation%!(EXTRA int=0)
Since organizations are similar to users, that probably means that they have an internal repository limit as well which is incorrectly applied.
[x]
):The text was updated successfully, but these errors were encountered: