[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Taler] Allow history rewrite on feature branches

From: Florian Dold
Subject: Re: [Taler] Allow history rewrite on feature branches
Date: Sat, 27 Apr 2019 00:32:20 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1


this is already implemented, albeit not documented yet.

If gitolite knows you as user $USER, then you can force push to branches
of the form


and if that's not working it's a bug.  I'll add this to the onboarding

- Florian

On 4/26/19 10:36 PM, Christian Grothoff wrote:
> On 4/26/19 9:50 PM, Lukas Großberger wrote:
>> Dear Taler team,
>> currently, a server side hook prevents people from force pushing (i.e.
>> rewriting version history).
>> I find amending commits or squashing commits to be quite useful to keep
>> the history of a feature branch tidy before merging.
>> How do you feel about making an exception in that hook for branches with
>> the prefix "feature/"?
>> Best, Lukas
> I'm generally OK with allowing force pushes for branches other than
> master.  However, I don't know what the best policy here is, i.e.
> whether we should allow anyone to force push everywhere, or say only
> $USER to branches starting with $USER.  ng0/Florian: you two usually
> have strong opinions on these kinds of matters, please just propose,
> implement and document (in onboarding manual) some sane policy here.

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]