You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 29, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 29, 2022. It is now read-only.
I think I figured this out. It means (maybe among other things) that one of the repos doesn't have the right permissions. Even though I was an owner on both incoming and outgoing repos, I needed to disable the "require 3rd party tokens" or something... one of my repos was configured to only allow some pre-granted apps from manipulating that. And Github Issue Mover wasn't authorized as an app in the repo.
Sorry, that's probably confusing, but hopefully it helps. I don't remember the exact details.
Activity
[-]ez is null error when trying to move issues[/-][+]ez on null error when trying to move issues[/+]alexsoble commentedon Feb 8, 2016
Getting the same error.
sethladd commentedon Feb 8, 2016
I think I figured this out. It means (maybe among other things) that one of the repos doesn't have the right permissions. Even though I was an owner on both incoming and outgoing repos, I needed to disable the "require 3rd party tokens" or something... one of my repos was configured to only allow some pre-granted apps from manipulating that. And Github Issue Mover wasn't authorized as an app in the repo.
Sorry, that's probably confusing, but hopefully it helps. I don't remember the exact details.
azenla commentedon Feb 9, 2016
This is actually a problem in the GitHub.dart library. See SpinlockLabs/github.dart#47 as well as #3 and #11.
I will see about fixing this in GitHub.dart.
ruebot commentedon Feb 12, 2016
Getting the same error.
lpanebr commentedon Oct 20, 2016
I've got this when the mentioned or participating collaborators were not available in the destination repo.
DonJayamanne commentedon Oct 26, 2016
Getting the same error.
Used to work in the past, not anymore.
tleyden commentedon Nov 15, 2016
For me it looks like it's failing for the same reason that @Ipanebr mentioned