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 <jcesarmob...@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.br...@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 <dvpdin...@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.br...@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-unsubscr...@cordova.apache.org > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > >
