I suppose we're interested in code proposal from the 23 still open PRs, not
the PR explanations nor the 117 closed ones.
perhaps reuse some logic from migrate-plugins.sh [1]
once you have cloned the full repo with the updated content, the critical
command is:
# Remove everything except the pat
I suppose we're interested in code proposal from the 23 still open PRs, not
the PR explanations nor the 117 closed ones.
perhaps reuse some logic from migrate-plugins.sh [1]
once you have cloned the full repo with the updated content, the critical
command is:
# Remove everything except the pat
On Wed, 21 Mar 2018 at 08:38, Jeff MAURY wrote:
> A pr has its own branch (refs/pull/prid/head)
>
sure but in this case the path is different (was svn plugins tree) so the
branch will not apply directly with the the new tree.
So it's easy to retrieve them but don't know how to recreate them on
A pr has its own branch (refs/pull/prid/head)
So it's easy to retrieve them but don't know how to recreate them on the
target repository
Hope this helps
Jeff
Le mar. 20 mars 2018 à 22:06, Olivier Lamy a écrit :
> Hi
> We have a lot of pr here https://github.com/apache/maven-plugins/pulls
>
> an
Hi
We have a lot of pr here https://github.com/apache/maven-plugins/pulls
any ideas how to migrate those pr to their new git plugin repo?
Cheers
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
