www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jake Farrell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-8228) Disable git force push on CloudStack repositories (at least)
Date Tue, 26 Aug 2014 04:03:57 GMT

     [ https://issues.apache.org/jira/browse/INFRA-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jake Farrell updated INFRA-8228:

    Status: Waiting for user  (was: Waiting for Infra)

There is no way to tell between a release branch and a non-release branch, disable all force
push events on CloudStack branch* ? Has this been discussed on the dev or pmc lists?

> Disable git force push on CloudStack repositories (at least)
> ------------------------------------------------------------
>                 Key: INFRA-8228
>                 URL: https://issues.apache.org/jira/browse/INFRA-8228
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: Rohit Yadav
>            Assignee: Jake Farrell
>            Priority: Critical
> Right now on CloudStack project repos, a committer can do a git force push on all branches
(did not check for master or release branches). Tested on a test branch and force push was
successful on repo: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=heads
> The repo's git hooks should ideally drop all force push events, please add/improve git
hook of the repos to not allow force push on at least master and release branches (such as
4.1, 4.2, 4.3 in CloudStack's case).

This message was sent by Atlassian JIRA

View raw message