You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Chris Brody <ch...@gmail.com> on 2019/01/16 15:22:00 UTC
Transferring Cordova issues on GitHub
Here is an example where I had to apply a clumsy workaround:
https://github.com/apache/cordova/issues/68
I submitted the following INFRA ticket:
https://issues.apache.org/jira/browse/INFRA-17671
Re: Transferring Cordova issues on GitHub
Posted by Bryan Ellis <er...@apache.org>.
There was already a discussion about this and about using Probot.
As said before and still, I am in favor of adding Probot.
Let's add it before it falls off the radar again.
Previous Thread:
https://lists.apache.org/thread.html/e2d9912052bc274f449e56fb2e4a1b518536c34a3146076d3a65c0d6@%3Cdev.cordova.apache.org%3E
+1 for Probot
On Thu, Jan 17, 2019 at 11:13 AM Chris Brody <ch...@gmail.com> wrote:
> I would favor using the Probot move app. Anyone else?
>
> I would be happy to raise another INFRA issue, with a link to this thread,
> if we get a couple more +1 votes on this idea.
>
> On Wed, Jan 16, 2019 at 8:39 PM Shazron <sh...@gmail.com> wrote:
>
> > Not sure what they think about installing Probot:
> > https://probot.github.io/apps/move/
> > Seems like a good compromise -- since we have write permissions for
> > the source and target repos.
> >
> > On Wed, Jan 16, 2019 at 11:47 PM Chris Brody <ch...@gmail.com>
> > wrote:
> > >
> > > Thanks guys. I completely get it that it is not possible to get what we
> > > want according to the existing combination of INFRA rules and GitHub
> > > behavior.
> > >
> > > I find this to be pretty bad for usability and am hopeful that we may
> be
> > > able to work towards a better solution, somehow. That is why I raised
> the
> > > INFRA issue in the first place.
> > >
> > > On Wed, Jan 16, 2019 at 10:43 AM julio cesar sanchez <
> > jcesarmobile@gmail.com>
> > > wrote:
> > >
> > > > They have answered that they can transfer the issues we tell them to,
> > but I
> > > > think it's easier/faster to just create a new one than creating an
> > infra
> > > > ticket so they move it.
> > > >
> > > > El mié., 16 ene. 2019 a las 16:39, Chris Brody (<
> chris.brody@gmail.com
> > >)
> > > > escribió:
> > > >
> > > > > I already saw that in the GitHub docs. I raised the INFRA issue in
> > hopes
> > > > > that we can find a solution, somehow.
> > > > >
> > > > > On Wed, Jan 16, 2019 at 10:33 AM Darryl Pogue <dvpdiner2@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > From the GitHub docs:
> > > > > > > To transfer an open issue to another repository, you must have
> > admin
> > > > > > permissions on the repository the issue is in and the repository
> > you're
> > > > > > transferring the issue to.
> > > > > >
> > > > > > I don't think there's anything INFRA can do to enable it, since
> > repo
> > > > > > admin isn't something they'll provide :(
> > > > > >
> > > > > > On Wed, Jan 16, 2019 at 7:22 AM Chris Brody <
> chris.brody@gmail.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > Here is an example where I had to apply a clumsy workaround:
> > > > > > > https://github.com/apache/cordova/issues/68
> > > > > > >
> > > > > > > I submitted the following INFRA ticket:
> > > > > > > https://issues.apache.org/jira/browse/INFRA-17671
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
>
Re: Transferring Cordova issues on GitHub
Posted by Chris Brody <ch...@gmail.com>.
I would favor using the Probot move app. Anyone else?
I would be happy to raise another INFRA issue, with a link to this thread,
if we get a couple more +1 votes on this idea.
On Wed, Jan 16, 2019 at 8:39 PM Shazron <sh...@gmail.com> wrote:
> Not sure what they think about installing Probot:
> https://probot.github.io/apps/move/
> Seems like a good compromise -- since we have write permissions for
> the source and target repos.
>
> On Wed, Jan 16, 2019 at 11:47 PM Chris Brody <ch...@gmail.com>
> wrote:
> >
> > Thanks guys. I completely get it that it is not possible to get what we
> > want according to the existing combination of INFRA rules and GitHub
> > behavior.
> >
> > I find this to be pretty bad for usability and am hopeful that we may be
> > able to work towards a better solution, somehow. That is why I raised the
> > INFRA issue in the first place.
> >
> > On Wed, Jan 16, 2019 at 10:43 AM julio cesar sanchez <
> jcesarmobile@gmail.com>
> > wrote:
> >
> > > They have answered that they can transfer the issues we tell them to,
> but I
> > > think it's easier/faster to just create a new one than creating an
> infra
> > > ticket so they move it.
> > >
> > > El mié., 16 ene. 2019 a las 16:39, Chris Brody (<chris.brody@gmail.com
> >)
> > > escribió:
> > >
> > > > I already saw that in the GitHub docs. I raised the INFRA issue in
> hopes
> > > > that we can find a solution, somehow.
> > > >
> > > > On Wed, Jan 16, 2019 at 10:33 AM Darryl Pogue <dv...@gmail.com>
> > > wrote:
> > > >
> > > > > From the GitHub docs:
> > > > > > To transfer an open issue to another repository, you must have
> admin
> > > > > permissions on the repository the issue is in and the repository
> you're
> > > > > transferring the issue to.
> > > > >
> > > > > I don't think there's anything INFRA can do to enable it, since
> repo
> > > > > admin isn't something they'll provide :(
> > > > >
> > > > > On Wed, Jan 16, 2019 at 7:22 AM Chris Brody <chris.brody@gmail.com
> >
> > > > wrote:
> > > > > >
> > > > > > Here is an example where I had to apply a clumsy workaround:
> > > > > > https://github.com/apache/cordova/issues/68
> > > > > >
> > > > > > I submitted the following INFRA ticket:
> > > > > > https://issues.apache.org/jira/browse/INFRA-17671
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > >
> > > > >
> > > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: Transferring Cordova issues on GitHub
Posted by Shazron <sh...@gmail.com>.
Not sure what they think about installing Probot:
https://probot.github.io/apps/move/
Seems like a good compromise -- since we have write permissions for
the source and target repos.
On Wed, Jan 16, 2019 at 11:47 PM Chris Brody <ch...@gmail.com> wrote:
>
> Thanks guys. I completely get it that it is not possible to get what we
> want according to the existing combination of INFRA rules and GitHub
> behavior.
>
> I find this to be pretty bad for usability and am hopeful that we may be
> able to work towards a better solution, somehow. That is why I raised the
> INFRA issue in the first place.
>
> On Wed, Jan 16, 2019 at 10:43 AM julio cesar sanchez <jc...@gmail.com>
> wrote:
>
> > They have answered that they can transfer the issues we tell them to, but I
> > think it's easier/faster to just create a new one than creating an infra
> > ticket so they move it.
> >
> > El mié., 16 ene. 2019 a las 16:39, Chris Brody (<ch...@gmail.com>)
> > escribió:
> >
> > > I already saw that in the GitHub docs. I raised the INFRA issue in hopes
> > > that we can find a solution, somehow.
> > >
> > > On Wed, Jan 16, 2019 at 10:33 AM Darryl Pogue <dv...@gmail.com>
> > wrote:
> > >
> > > > From the GitHub docs:
> > > > > To transfer an open issue to another repository, you must have admin
> > > > permissions on the repository the issue is in and the repository you're
> > > > transferring the issue to.
> > > >
> > > > I don't think there's anything INFRA can do to enable it, since repo
> > > > admin isn't something they'll provide :(
> > > >
> > > > On Wed, Jan 16, 2019 at 7:22 AM Chris Brody <ch...@gmail.com>
> > > wrote:
> > > > >
> > > > > Here is an example where I had to apply a clumsy workaround:
> > > > > https://github.com/apache/cordova/issues/68
> > > > >
> > > > > I submitted the following INFRA ticket:
> > > > > https://issues.apache.org/jira/browse/INFRA-17671
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > >
> > > >
> > >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Transferring Cordova issues on GitHub
Posted by Chris Brody <ch...@gmail.com>.
Thanks guys. I completely get it that it is not possible to get what we
want according to the existing combination of INFRA rules and GitHub
behavior.
I find this to be pretty bad for usability and am hopeful that we may be
able to work towards a better solution, somehow. That is why I raised the
INFRA issue in the first place.
On Wed, Jan 16, 2019 at 10:43 AM julio cesar sanchez <jc...@gmail.com>
wrote:
> They have answered that they can transfer the issues we tell them to, but I
> think it's easier/faster to just create a new one than creating an infra
> ticket so they move it.
>
> El mié., 16 ene. 2019 a las 16:39, Chris Brody (<ch...@gmail.com>)
> escribió:
>
> > I already saw that in the GitHub docs. I raised the INFRA issue in hopes
> > that we can find a solution, somehow.
> >
> > On Wed, Jan 16, 2019 at 10:33 AM Darryl Pogue <dv...@gmail.com>
> wrote:
> >
> > > From the GitHub docs:
> > > > To transfer an open issue to another repository, you must have admin
> > > permissions on the repository the issue is in and the repository you're
> > > transferring the issue to.
> > >
> > > I don't think there's anything INFRA can do to enable it, since repo
> > > admin isn't something they'll provide :(
> > >
> > > On Wed, Jan 16, 2019 at 7:22 AM Chris Brody <ch...@gmail.com>
> > wrote:
> > > >
> > > > Here is an example where I had to apply a clumsy workaround:
> > > > https://github.com/apache/cordova/issues/68
> > > >
> > > > I submitted the following INFRA ticket:
> > > > https://issues.apache.org/jira/browse/INFRA-17671
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> > >
> >
>
Re: Transferring Cordova issues on GitHub
Posted by julio cesar sanchez <jc...@gmail.com>.
They have answered that they can transfer the issues we tell them to, but I
think it's easier/faster to just create a new one than creating an infra
ticket so they move it.
El mié., 16 ene. 2019 a las 16:39, Chris Brody (<ch...@gmail.com>)
escribió:
> I already saw that in the GitHub docs. I raised the INFRA issue in hopes
> that we can find a solution, somehow.
>
> On Wed, Jan 16, 2019 at 10:33 AM Darryl Pogue <dv...@gmail.com> wrote:
>
> > From the GitHub docs:
> > > To transfer an open issue to another repository, you must have admin
> > permissions on the repository the issue is in and the repository you're
> > transferring the issue to.
> >
> > I don't think there's anything INFRA can do to enable it, since repo
> > admin isn't something they'll provide :(
> >
> > On Wed, Jan 16, 2019 at 7:22 AM Chris Brody <ch...@gmail.com>
> wrote:
> > >
> > > Here is an example where I had to apply a clumsy workaround:
> > > https://github.com/apache/cordova/issues/68
> > >
> > > I submitted the following INFRA ticket:
> > > https://issues.apache.org/jira/browse/INFRA-17671
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
>
Re: Transferring Cordova issues on GitHub
Posted by Chris Brody <ch...@gmail.com>.
I already saw that in the GitHub docs. I raised the INFRA issue in hopes
that we can find a solution, somehow.
On Wed, Jan 16, 2019 at 10:33 AM Darryl Pogue <dv...@gmail.com> wrote:
> From the GitHub docs:
> > To transfer an open issue to another repository, you must have admin
> permissions on the repository the issue is in and the repository you're
> transferring the issue to.
>
> I don't think there's anything INFRA can do to enable it, since repo
> admin isn't something they'll provide :(
>
> On Wed, Jan 16, 2019 at 7:22 AM Chris Brody <ch...@gmail.com> wrote:
> >
> > Here is an example where I had to apply a clumsy workaround:
> > https://github.com/apache/cordova/issues/68
> >
> > I submitted the following INFRA ticket:
> > https://issues.apache.org/jira/browse/INFRA-17671
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: Transferring Cordova issues on GitHub
Posted by Darryl Pogue <dv...@gmail.com>.
From the GitHub docs:
> To transfer an open issue to another repository, you must have admin permissions on the repository the issue is in and the repository you're transferring the issue to.
I don't think there's anything INFRA can do to enable it, since repo
admin isn't something they'll provide :(
On Wed, Jan 16, 2019 at 7:22 AM Chris Brody <ch...@gmail.com> wrote:
>
> Here is an example where I had to apply a clumsy workaround:
> https://github.com/apache/cordova/issues/68
>
> I submitted the following INFRA ticket:
> https://issues.apache.org/jira/browse/INFRA-17671
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org