[
https://issues.apache.org/jira/browse/FLEX-33175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815676#comment-13815676
]
Alex Harui commented on FLEX-33175:
-----------------------------------
A similar discussion was going on at members@ and these two snippets came out
of it which might be useful.
1) A member wrote: "So we never, ever pull anything into the GitHub repo
directly. For my own pull requests, once it's been reviewed/passed CI/etc, I do
a git pull --rebase origin (ASF branch the change is going to), force-push to
my GitHub fork so that the hash on the pull request is updated, and then do
"git push origin (local branch):(ASF branch the change is going to). Then the
PR gets automatically closed on the next ASF->GH repo sync."
2) An Infra person suggests using something called gitpubsub.
> How do integrate Github pull requests into current SVN repository
> -----------------------------------------------------------------
>
> Key: FLEX-33175
> URL: https://issues.apache.org/jira/browse/FLEX-33175
> Project: Apache Flex
> Issue Type: Question
> Reporter: Justin Mclean
>
> We need a way to apply github pull requests (from the Flex github mirror)
> into the current SVN repository.
> 1. How do we generate patch file from Github?
> 2. How we we apply the github patch to the current SVN repo?
> 3. How do we close the github pull request?
> Note that 1 + 2 will also help people working with git.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
