infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15859) branch-3 should be deleted in the Hadoop git repo
Date Fri, 19 Jan 2018 21:11:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-15859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332900#comment-16332900
] 

Jason Lowe commented on INFRA-15859:
------------------------------------

I assumed there was a hook to prevent this, and that seems to be the case.  I just tried it
now and it failed:
{noformat}
$ git push origin :branch-3
remote: Rewinding refs/heads/branch-3 is forbidden.
remote: 
To https://jlowe@git-wip-us.apache.org/repos/asf/hadoop.git
 ! [remote rejected] branch-3 (pre-receive hook declined)
{noformat}

> branch-3 should be deleted in the Hadoop git repo
> -------------------------------------------------
>
>                 Key: INFRA-15859
>                 URL: https://issues.apache.org/jira/browse/INFRA-15859
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: Jason Lowe
>            Assignee: Chris Thistlethwaite
>            Priority: Major
>
> Recently a committer accidentally created a "branch-3" branch in the Hadoop repository,
git-wip-us.apache.org/repos/asf/hadoop.git.  This is causing a lot of confusion since there
is already a "branch-3.0" branch, and some committers are committing their code that should
be on branch-3.0 into branch-3.
> We would like branch-3 to be deleted so the confusion and mis-commits are reduced.  I
am assuming there is a push hook that prevents committers from doing this directly (if not
there probably should be one), hence the INFRA request.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message