[x]):Relevant part of the ini
[repository]
ENABLE_PUSH_CREATE_ORG = true
ENABLE_PUSH_CREATE_USER = true
Now, let's try and auto-create org/repo on push
git remote add gitea-remote-new-org [email protected]:neworgname/reponame.git
git push -u --set-upstream gitea-remote-new-org master
Unfortunately, the result is
Unable to get owner: neworgname user does not exist [uid: 0, name: neworgname, keyid: 0]
However, this works:
git remote add gitea-remote-existing-org [email protected]:existingorgname/reponame.git
git remote add gitea-remote-existing-user [email protected]:existinguser/reponame.git
git push -u gitea-remote-existing-org master
git push -u gitea-remote-existing-user master
Imho, I miss knowledge/expertise, misunderstand the purpose of ENABLE_PUSH_CREATE or a bug has been discovered.
In case, the purpose of those switches are granular control, ie, already existing user/organization namespaces and absent repos, then this is likely a feature request.
Desired result - whatever is pushed to gitea should auto-create namespaces, provided the user has enough permissions.
Any advise/comment is much appreciated!
PUSH_CREATE_ORG allows you to create repositories for an existing organizations. It cannot just create organizations.
Similarly PUSH_CREATE_USER allows you to create repositories for existing users themselves.
Most helpful comment
PUSH_CREATE_ORG allows you to create repositories for an existing organizations. It cannot just create organizations.
Similarly PUSH_CREATE_USER allows you to create repositories for existing users themselves.