Repository navigation
Import issues from VSO #2
Description
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.
Metadata
Metadata
Assignees
Labels
No labels
Activity
ealexjordan commentedon Jan 19, 2016
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.
ealexjordan commentedon Jan 20, 2016
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.
andyleejordan commentedon Jan 22, 2016
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.
ealexjordan commentedon Jan 22, 2016
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.
Import PSReadLine sources
Import PSReadLine sources
# This is a combination of 3 commits.
Temporary workaround #2 to fix the PSVersion issue in beta.1 release
Temporary workaround #2 to fix the PSVersion issue in beta.1 release (#…
fix codefactor issues PowerShell#2
Attempt #2
SPLIT-PATH should reject 2 positional parameters
Verify SPLIT-PATH errors given parameter #2
Merge pull request PowerShell#2 from stevenebutler/encodinghelper-patch
Import PSReadLine sources
# This is a combination of 3 commits.
Temporary workaround PowerShell#2 to fix the PSVersion issue in beta.…