infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Thistlethwaite (JIRA)" <>
Subject [jira] [Commented] (INFRA-17131) Protecting branches in Gitbox experiment against force push
Date Fri, 12 Oct 2018 13:55:00 GMT


Chris Thistlethwaite commented on INFRA-17131:

master should've been protected by default when the migration happened, not sure why that
didn't go as I'm the one that did the migration. It was a bulk move so perhaps the script
didn't finish correctly as the repo descriptions still contained "Mirror of". 

At any rate, master is now protected and the descriptions are updated.

I agree, protecting tags and release branches might get a bit busy and don't have a good answer
besides just putting in tickets when you want them protected. If it's something that gets
to be too much, we'll either start saying "no" or build something to do it for us.

> Protecting branches in Gitbox experiment against force push
> -----------------------------------------------------------
>                 Key: INFRA-17131
>                 URL:
>             Project: Infrastructure
>          Issue Type: Project
>          Components: Git, GitBox, Github
>            Reporter: Rafael Weingärtner
>            Assignee: Chris Thistlethwaite
>            Priority: Major
> Hello Infra team, 
> I was wondering. Is it possible for you to enable branch protection in CloudStack repos?
I mean, we would like to protect certain branches (e.g. master, and LTSs) against force pushes.
Is that possible? I tried to find a configuration in Github, but I was not able to see the
settings of the repository.

This message was sent by Atlassian JIRA

View raw message