gitea: User in Organisation has no repo limit but the user itself has a limit of 0: Cannot create repo in organisation

-1 means derive from global configuration which is in your instance app.ini. -1 doesn’t mean no limitation.

@Commifreak and @lunny it always meant no limit

Ah, yes. They made some confusions. The configuration item MAX_CREATION_LIMIT = -1 means globally no limitation. But the value -1 in the UI of org or user setting in admin means deriving from global configuration. The two -1 have different concepts.

Closed by accident.

-1 means derive from global configuration which is in your instance app.ini. -1 doesn’t mean no limitation.

OK. Maybe we need another limitation. We already have these limitations.

• The number which user could create around the instance, not only under his name
• The number for an organization could create under the organization
• The number which a user could create organization

So I think we may need another one.

• The number which user could create in all his organization. That means we should change the meaning of the first limitation as the number which user could create under his name.

I think it is easier to tackle this problem just defining MAX_USER_REPOS and MAX_ORG_REPOS. So if any user is creating a repo for himself validate MAX_USER_REPOS and if the user is creating a repo for some organization just validate MAX_ORG_REPOS

I see, It’s a ui bug, should recheck limit when switch Owner