Hi,
On Tue, 2018-01-23 at 15:05 +0100, Stefan Egli wrote:
> Sounds like a good idea to start with disallowing --force for now,
> given
> there is --force-with-lease for emergencies. The unfortunate bit is
> perhaps that this opens up a way to modify history without noticing
> (which
> is what I've
rand Delacretaz [mailto:bdelacre...@apache.org]
>Sent: Tuesday, January 23, 2018 8:49 AM
>To: dev
>Subject: Re: Git force push
>
>EXTERNAL
>
>On Tue, Jan 23, 2018 at 2:33 PM, Stefan Seifert
>wrote:
>> i would also vote for *not* allowing push --force..
>
>+1, my u
ary 23, 2018 8:49 AM
To: dev
Subject: Re: Git force push
EXTERNAL
On Tue, Jan 23, 2018 at 2:33 PM, Stefan Seifert wrote:
> i would also vote for *not* allowing push --force..
+1, my understanding is that one can destroy history with that...which
we don't want.
I have never used -
On Tue, Jan 23, 2018 at 2:33 PM, Stefan Seifert wrote:
> i would also vote for *not* allowing push --force..
+1, my understanding is that one can destroy history with that...which
we don't want.
I have never used --force-with-lease so far but according to [1] it
only allows you to force-push if
i would also vote for *not* allowing push --force
stefan
>-Original Message-
>From: Oliver Lietz [mailto:apa...@oliverlietz.de]
>Sent: Tuesday, January 23, 2018 1:21 PM
>To: dev@sling.apache.org
>Subject: Git force push
>
>Hi,
>
>can we have a simple rule (
I just stumbled upon a problem where I did a commit with a wrong author
email (in SLING-7407) and "thanks" to force push I was able to correct
this. Not saying it is a good idea to do this often though .. ;)
Cheers,
Stefan
On 23.01.18, 13:26, "Radu Cotescu" wrote:
>Hi Oliver,
>
>Shouldn't we *n
Hi Oliver,
Shouldn't we *never* allow force push?
Cheers,
Radu
On Tue, 23 Jan 2018 at 14:20 Oliver Lietz wrote:
> Hi,
>
> can we have a simple rule (allow vs deny) for git push --force?
>
> Thanks,
> O.
>
>
Hi,
can we have a simple rule (allow vs deny) for git push --force?
Thanks,
O.
