I have setup force push protection on master, 2.8.x, 2.7.x, and for good
measure, also 2.6.x and 2.5.x
(and the corresponding GeoTools branches too).
We should remember to perform this step when cutting new stable branches,
every six months
For reference, here is how it's done manually:
https://h
Think we got general agreement and can make use of "project" when the
functionality is available.
--
Jody Garnett
On 14 October 2015 at 14:01, Ben Caradoc-Davies wrote:
> +1 to protect master, stable, and maintenance. Force push too often ends
> badly for all concerned.
>
> -1 for status checks
+1 to protect master, stable, and maintenance. Force push too often ends
badly for all concerned.
-1 for status checks. I agree that they will be a hindrance. We would
need much greater build stability before we even contemplated status checks.
Kind regards,
Ben.
On 14/10/15 22:29, Stefano Cos
On Wed, Oct 14, 2015 at 6:00 PM, Jody Garnett
wrote:
> We do not use force push often, maybe twice? I think we could turn that
> off.
>
>
The cases in which it happened (that I can remember) it was actually due to
a typo and
it screwed up the history... took some fiddling with the github rest api
We do not use force push often, maybe twice? I think we could turn that off.
I can see why the status check is added, but we are not that concerned with
having a non branching history due to our modular nature.
On Wed, Oct 14, 2015 at 2:42 AM Andrea Aime
wrote:
> On Wed, Oct 14, 2015 at 11:29
On Wed, Oct 14, 2015 at 11:29 AM, Stefano Costa <
stefano.co...@geo-solutions.it> wrote:
> IMHO, we should definitely make master, stable and maintenance protected
> branches.
>
Agreed.
>
> Not sure about required status checks: in some occasions (e.g. small
> changes) they may turn into a usel
IMHO, we should definitely make master, stable and maintenance protected
branches.
Not sure about required status checks: in some occasions (e.g. small
changes) they may turn into a useless hindrance.
On Wed, Oct 14, 2015 at 8:13 AM, Andrea Aime
wrote:
> https://github.com/blog/2051-protected-b
https://github.com/blog/2051-protected-branches-and-required-status-checks
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Mas
