3 ms·
Its actually pretty cool that all the google code issues got turned GitHub issues, in the same exact order as the google code issues such that the issues number
by nemothekid 12y ago
Its actually pretty cool that all the google code issues got turned GitHub issues, in the same exact order as the google code issues such that the issues numbers are still consistent on Github.
- blowski 12y agoI'm guessing they did it with an import script - something like http://www.iqandreas.com/github-issues-import/configuration/#enterprise http://www.iqandreas.com/github-issues-import/configuration/...
- giovannibajo1 12y agoI went through a similar migration last month for PyInstaller, and we couldn't find a way to set the original date for issues/comments; the best solution was to add the date/time as part of the comment; see just one example here: https://github.com/pyinstaller/pyinstaller/issues/830 https://github.com/pyinstaller/pyinstaller/issues/830 The script you linked does the same (we used a different now). We even contacted GitHub and they said we were out of luck, very sorry. Now, I see golang has perfectly migrated all the timestamps. I wonder how they did that. If they used some private APIs, I would be very annoyed with GitHub support.