Allow non-admin users to create repositories under projects

[gitblit]

Originally reported on Google Code with ID 351

Feature request:
Allow users/teams to create and manage repositories under projects (project/.*).


Reason:
Users always want to be self-organized and as much independent from the IT team as
possible, they should have access only on specific projects, not full site administrators.

In addition probably inherited rights or default rights feature would be great to make
their job easier.

Reported by tomposmiko on 2013-12-11 18:34:18

[gitblit]

Issue 710 has been merged into this issue.

Reported by James.Moger on 2014-04-26 13:59:13

[gitblit]

Is there any update on this issue? We'd absolutely love to have this feature as well!
It'd be awesome if teams could create their own repositories without requiring full
admin permissions.

Reported by gibwar on 2014-06-16 19:26:24

[gitblit]

There is progress on this issue.  It is one of the major enhancements planned for 1.7.0.
 Some of the precursor changes needed to complete this feature have landed in 1.6.0
which will be released later today or tomorrow.  There are draft changes for project
administration in ticket 75, but nothing that you should try using yet.  :)

https://dev.gitblit.com/tickets/gitblit.git/75

Reported by James.Moger on 2014-06-16 19:35:22

• Status changed: Started
• Labels added: Milestone-1.7.0

[gitblit]

Why not expand the create permission to allow create anywhere and not just the personal
directory?  I don't see how a user can use create to do any more harm than a user misusing
push.  Granted Gitblit doesn't have a move repository feature should one be created
in the wrong place, but that's easily doable outside Gitblit if necessary.  Widening
the definition of the create permission seems to distribute a lot of "regular" admin
tasks at shops that regularly create repos, and is a super simple change.  What are
the things I'm missing that make this simple idea a bad one?

We just started using Gitblit to replace a homebrew solution, and I've made the trivial
modification to do the above.  https://github.com/smckown/gitblit/commit/320cae10f90f2b5103c8fcb18bc01a6c4b2cf865

Reported by rsmckown on 2014-10-01 00:50:52

[gitblit]

Moving a repo is just a rename.

Many installations do want enhanced create and repo management permissions, but they
do not want global create.

Reported by James.Moger on 2014-10-01 01:39:31

[gitblit]

Rename as admin user: I missed this, thanks.  This feature makes global create a slam
dunk for us, as there seems no create error which couldn't be trivially addressed solely
within the Gitblit UI.

Gitblit is a nice product, and the code is quite clean and readable.  It's a perfect
solution for us, even if we end up hacking a couple of local patches that make no sense
for others.  Thanks for sharing your hard work!

Reported by rsmckown on 2014-10-01 15:08:38

[pilarragorri]

Hi,

What is the status on this enhancement?

We are currently working on the expansion of gitblit to other teams and the ability to be able to create repositories under projects for non-admin users would be really useful.

[gitblit]

Hi @pilarragorri, this was started a while ago but it remains unfinished and no one is presently engaged in improving the create repository permissions.

[kwoot]

Maybe @pilarragorri can arrange a budget for the development of this feature?