Node: meta: issue transfer

Created on 31 Oct 2018  路  7Comments  路  Source: nodejs/node

Can we utilize this new GitHub feature to transfer wrong repo issues? It seems, only admins can do this. Would it be too burdensome to ping them each time?

https://blog.github.com/changelog/2018-10-30-issue-transfer/
https://help.github.com/articles/transferring-an-issue-to-another-repository/

Most helpful comment

I mostly meant nodejs/help, it was near 50% of the wrong repo cases so far.

All 7 comments

As I understand it, the person moving the issue has to be admin in both repos. From what I typically see, the other repo is outside of the nodejs org even (e.g. npm, third-party modules), so the likelyhood of a nodejs org admin also being the admin for that second repo is going to be near zero.

I mostly meant nodejs/help, it was near 50% of the wrong repo cases so far.

Would it be too burdensome to ping them each time?

Can't speak for other org owners, but I don't mind being pinged for this.

I don't mind it either

Is there a group of the repository admins we can ping? Or a group of the repository admins who do not mind to be pinged? Should we create one if not?

Is there a group of the repository admins we can ping? Or a group of the repository admins who do not mind to be pinged? Should we create one if not?

I'd prefer not to create a new team just for this sort of thing, but won't stop someone else from doing it if they feel differently.

I'm going to close this because it seems we've arrived at an _ad hoc_ procedure. We can iterate and/or document later if there's benefit.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

willnwhite picture willnwhite  路  3Comments

cong88 picture cong88  路  3Comments

akdor1154 picture akdor1154  路  3Comments

filipesilvaa picture filipesilvaa  路  3Comments

mcollina picture mcollina  路  3Comments