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 2014/02/13 07:54:20 UTC

[jira] [Commented] (INFRA-7311) Indefinite mirroring of orphaned refs in GitHub mirror

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

Paul Joseph Davis commented on INFRA-7311:
------------------------------------------

+1 to figuring out how to make this happen. Currently GitHub runs the mirror scripts so I don't think there's anything we can do other than ask nicely. The docs on how GitHub mirroring works are roughly non-existent and I've never interacted with their support to know how likely it is for this to happen.

Originally I was planning on writing hooks that'd queue up pushes to their infra but the read-only mirrors had the GitHub mirroring already configured. I wonder if it'd be possible to undo that and write our own which might make the whole thing a lot more reactive as well.

> Indefinite mirroring of orphaned refs in GitHub mirror
> ------------------------------------------------------
>
>                 Key: INFRA-7311
>                 URL: https://issues.apache.org/jira/browse/INFRA-7311
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Git
>            Reporter: Christopher Tubbs
>            Priority: Minor
>
> I think it'd be great if it were possible to force the GitHub mirror to prune deleted refs, rather than mirror them indefinitely. There's a lot of temporary branches... sometimes they get deleted and then another one gets created with the same name.
> For instance, in the Accumulo project, there's several deleted branches/tags that have been merged in to the main development branches long ago and subsequently deleted, but they still show up in the GitHub mirror. I'm wondering if there's a mirroring option that would address that issue automatically (or at all).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)