Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: github protected branches
by
LasLabs, Dave Lasley
Admins can be allowed to push to protected branches, but that’s about as granular as it gets unfortunately.
— Dave Lasley
On Dec 21, 2016, at 6:38 AM, Bidoul@pad.odoo-community.org wrote:Hi Holger,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.-sbiOn Wed, Dec 21, 2016 at 3:23 PM, Holger Brunn <hbrunn@therp.nl> 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: holger@therp.nl web: http://therp.nl phone: +31 (0)20 3093096______________________________
_________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe _______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe
Reference
-
github protected branches
byAcsone SA/NV, Stéphane Bidoul-
Re: github protected branches
byClosingAp Open Source Integrators Europe, LDA, Daniel Reis
-