You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Paul Joseph Davis (JIRA)" <ji...@apache.org> on 2010/12/06 00:04:11 UTC

[jira] Updated: (INFRA-3162) Hook: No history rewriting

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

Paul Joseph Davis updated INFRA-3162:
-------------------------------------

    Attachment: update

This hook prevents rewriting the of the HEAD branch (defaults to refs/heads/master, but the git.apache.org clones switch it to refs/heads/trunk to match SVN).

I opted to only enforce this for the HEAD branch because it'd otherwise just cause lots of pain in feature branches. A second place I would also like to enforce this is in version branches. This would be quite possible but there are a few methods we could use to implement it.

One would be to say that any branch that has a commit that's been taged since its split from trunk, which while automagical seems like it could lead to weird issues in restricting other work. Alternatively, we could just make it part of the process that version branches are prefixed with something like rel, so we'd have rel/1.0.x rel/1.1.x etc etc. That's also assuming that we want to enforce such things. Also, it'd be possible to make it configurable as well.

Anyway, basic no-rewrite appears to work. 

> Hook: No history rewriting
> --------------------------
>
>                 Key: INFRA-3162
>                 URL: https://issues.apache.org/jira/browse/INFRA-3162
>             Project: Infrastructure
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Paul Querna
>            Priority: Trivial
>         Attachments: update
>
>
> Do not allow history rewriting / git push --force.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.