Contributors mailing list archives
Re: github protected branchesby
Acsone SA/NV, Stéphane Bidoul
As far as I could understand, that kind of protection (ie verifiying that travis-ci succeeded) can't be bypassed on a per-user basis.
On Wed, Dec 21, 2016 at 3:23 PM, Holger Brunn <firstname.lastname@example.org> wrote:
> Direct push must be allowed for these tools to function properly, so I > deactivated the mandatory travis check protection on OCA/project for now. shouldn't we better add the account used by the tools to the group that can push on protected branches? Protected branches are a good thing to avoid accidental `push --force`s messing up everything. This happened in the past. -- Therp - Maatwerk in open ontwikkeling Holger Brunn - Ontwerp en implementatie mail: email@example.com web: http://therp.nl phone: +31 (0)20 3093096