Changes to branch management
jkt at kde.org
Wed Dec 24 16:04:02 GMT 2014
On Wednesday, 24 December 2014 01:57:15 CEST, Ben Cooksley wrote:
> Unfortunately i'm not sure if Gitolite's ACL mechanisms let us
> differentiate between tags and branches so if we allow anyone to
> delete branches they'll probably be able to do the same for tags.
Are the generated config files or the scripts for generating gitolite's
config files available somewhere? The Gitolite setup I'm familiar with uses
explicit qualifiers such as "refs/heads/" and "refs/tags/" when setting up
ACLs. Do you use something different on git.k.o? If not, then managing tags
separately from branches should come for free.
The way I see it, there are two reasonable alternatives with the current
1) Everybody can create, delete and force-push to all branches except the
"reserved" ones (kde/*, master, stable,... see the list).
2) People are free to create, delete and force-push to all branches below
my/$username/ (in my case, tat would be my/jkt/foo for example). Only repo
owners can create, delete and force-push to arbitrary branch names.
Deciding which of these to use should be just a matter of style. Both seem
very sensible to me, and they will definitely present an improvement over
the current status where people can create, but not cleanup afterwards.
With kind regards,
Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/
More information about the kde-core-devel