Repository navigation
Import issues from VSO #2
Description
Activity
Wrote a small tool to assist with doing this over the weekend. I'll test the VSO issues import on a private repo, run it by people, and then do the real deal. I expect to have this done in an hour or so.
Going to perform the import of VSO issues to GitHub tonight. If you don't want 400+ emails I would recommend temporarily setting GitHub settings to not email notifications.
We didn't end up importing last night as, after a conversation with GitHub support, we were pointed to an unreleased-but-available new API endpoint that allows bulk importing without sending 17,000+ emails and that will allow us to keep the original creation date and creator. A (@ealexjordan) is updating the importer.
Everything moved over to GitHub successfully. All VSO imported issues are labeled with "VSO Import." There's probably a bit of clean up to do, but everything came over correctly. Closing issue.
- added a commit that references this issue
on Apr 27, 2016 - added a commit that references this issue
on Aug 30, 2016 - added a commit that references this issue
on Nov 20, 2016 - added a commit that references this issue
on Aug 2, 2018 - added a commit that references this issue
on Aug 14, 2018 - added 2 commits that reference this issue
on Jun 14, 2020 - added a commit that references this issue
on Jan 7, 2024
Need to import our backlog of issues from VSO.
We can link an Excel spreadsheet to the VSO team to get the issues, then export to CSV, and import to GitHub using Octokit.