4 ms·

You make a good point about the just-move-to-Git[whatever] being the entrenched social aspect of many repos! I can't imagine if, say the day comes when develope

You make a good point about the just-move-to-Git[whatever] being the entrenched social aspect of many repos! I can't imagine if, say the day comes when developers flee GH en-masse, it will be at all easy to retain the discussion history behind repos.

mitochondrion 8y ago
Why not just scrape the site? I don’t see what the problem is.
pmontra 8y ago
There is an API https://developer.github.com/v3/issues/ https://developer.github.com/v3/issues/ It could be not trivial to map those data into the new destination, especially if they don't have an API too. This is how to programmatically create a new issue on GitLab https://docs.gitlab.com/ee/api/issues.html#new-issue https://docs.gitlab.com/ee/api/issues.html#new-issue and in Bitbucket https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Busername%7D/%7Brepo_slug%7D/issues#post https://developer.atlassian.com/bitbucket/api/2/reference/re...
- JetSpiegel 8y ago
  Gitlab already support this, no need to go with home grown bit banging. https://docs.gitlab.com/ee/user/project/import/github.html https://docs.gitlab.com/ee/user/project/import/github.html