[jboss-jira] [JBoss JIRA] (DROOLS-1769) All release branches should be protected from a force push

[Michael Biarnes Kiefer (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479246#comment-13479246 ] 

Michael Biarnes Kiefer commented on DROOLS-1769:
------------------------------------------------

response of GitHub guys:

Hi Michael,
my question was: if it is possible to protects automatically new created reps and it's branches in our organization.

===
Thanks for reaching out to GitHub Support!

I'm afraid that isn't currently possible. This sounds like it could be pretty useful so I've added your suggestion to our internal Feature Request List.

I can't promise that we will implement this feature now or in the future, but your feedback has definitely been noted and is super appreciated.

Cheers,
John
GitHub Support

> All release branches should be protected from a force push
> ----------------------------------------------------------
>
>                 Key: DROOLS-1769
>                 URL: https://issues.jboss.org/browse/DROOLS-1769
>             Project: Drools
>          Issue Type: Enhancement
>          Components: build
>            Reporter: Geoffrey De Smet
>            Assignee: Michael Biarnes Kiefer
>
> There are 2 ways to protect a GitHub repository/branch from force pushing:
> 1) a backend switch (not available in their UI) to disable force pushing for the entire repo (OLD)
> 2) "protected branches" in the "settings" menu of each repo, in the submenu "branches".
> Some repositories, such as "drools" and "optaplanner", have 1), so all their branches are immune to force pushing.
> Newer repositories, such as "optaplanner-wb" probably don't have 1).
> All repositories seem to have 2) for the following branches: master, 6.4.x, 6.5.x.
> BUT NOT 7.3.x etc. That's wrong: this means optaplanner-wb's 7.3.x branch is not protected against force pushes.
> All release branches (7.0.x, 7.1.x, ...) should be protected against force pushing. This includes future release branches, so the release procedure should be adjusted accordingly.
> We should ask github if there's a way to automatically add all new branches to "protected branches".



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)