META: migrate urbit/urbit issues about arvo

[juped]

I'm in the middle of this already

[ohAitch]

Empirically wontfix

[Fang-]

Moving issues isn't natively supported by GitHub, but there seems to be third party tooling for it. I can probably find some time tomorrow or over the weekend to do the needed house-cleaning on the urbit/urbit issues.

[ohAitch]

There's 100 of them so getting the u3/non-u3 tags up to date might take some sorting, but if you're up for it that would be great!

…

On Thu, Jan 11, 2018 at 3:34 PM, Fang ***@***.***> wrote: Moving issues isn't natively supported by GitHub, but there seems to be third party tooling for it. I can probably find some time tomorrow or over the weekend to do the needed house-cleaning on the urbit/urbit issues. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABxXhs4N7unhAp4HAK3_u4b7mXOkB6a9ks5tJpqFgaJpZM4Heh2S> .

[Fang-]

Looks like this was used, and it seems to be the nicest tool around.

It advises to use a dedicated bot account for this, as it becomes the author of all imported issues and their comments. It doesn't seem we have any such account yet. Any objections to me creating one and granting it the relevant permissions? cc @galenwp

[Fang-]

Alright, I went over all of them and moved the ones where it was obvious to me the issue didn't lay (even partially) in vere. Some were a bit unclear (ie 828, 832) to me without taking the deep dive, so I left those untouched. For issues where reproduction was trivial, I gave that a shot before moving or closing appropriately.

There are 15 issues that couldn't be moved automatically, the tool failing with:

ERROR: There was a problem importing the issues.
422 Unprocessable Entity
DETAILS: Validation Failed

These are the yet-unmoved issues:

323 352 353 358 359
370 375 407 613 630
653 686 687 711 717

I'll have to either dive into the tool's code/dependencies to see what's tripping it up, or just move them over manually.

(Sorry for the notification spam this caused, everybody.)