You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2012/07/29 11:32:34 UTC

[jira] [Created] (INFRA-5097) Push changes to GitHub

Jukka Zitting created INFRA-5097:
------------------------------------

             Summary: Push changes to GitHub
                 Key: INFRA-5097
                 URL: https://issues.apache.org/jira/browse/INFRA-5097
             Project: Infrastructure
          Issue Type: Improvement
      Security Level: public (Regular issues)
          Components: Git
            Reporter: Jukka Zitting


Currently our GitHub mirrors at https://github.com/apache are updated by GitHub periodically pulling changes from http://git.apache.org/. This introduces some update delay and prevents things like the automatic closing of merged pull requests.

I asked GitHub about this and they're fine with us pushing changes to them (their mirroring script won't get confused). Thus the only thing we need is a script that takes a repository and pushes all changes to the matching repository at GitHub.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (INFRA-5097) Push changes to GitHub

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443485#comment-13443485 ] 

#asfinfra IRC Bot commented on INFRA-5097:
------------------------------------------

<danielsh> dup of INFRA-4641

                
> Push changes to GitHub
> ----------------------
>
>                 Key: INFRA-5097
>                 URL: https://issues.apache.org/jira/browse/INFRA-5097
>             Project: Infrastructure
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jukka Zitting
>
> Currently our GitHub mirrors at https://github.com/apache are updated by GitHub periodically pulling changes from http://git.apache.org/. This introduces some update delay and prevents things like the automatic closing of merged pull requests.
> I asked GitHub about this and they're fine with us pushing changes to them (their mirroring script won't get confused). Thus the only thing we need is a script that takes a repository and pushes all changes to the matching repository at GitHub.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (INFRA-5097) Push changes to GitHub

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

#asfinfra IRC Bot closed INFRA-5097.
------------------------------------

    Resolution: Duplicate
    
> Push changes to GitHub
> ----------------------
>
>                 Key: INFRA-5097
>                 URL: https://issues.apache.org/jira/browse/INFRA-5097
>             Project: Infrastructure
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jukka Zitting
>
> Currently our GitHub mirrors at https://github.com/apache are updated by GitHub periodically pulling changes from http://git.apache.org/. This introduces some update delay and prevents things like the automatic closing of merged pull requests.
> I asked GitHub about this and they're fine with us pushing changes to them (their mirroring script won't get confused). Thus the only thing we need is a script that takes a repository and pushes all changes to the matching repository at GitHub.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira