My team and I have been using private GitHub Repos for a long time, but found out that this doesn’t suit our needs anymore.
So we decided to migrate to Bitbucket (we took a deeper look into JIRA+Stash (both also products by Atlassian) but at the time of writing this solution is a bit to overpowered for our needs and the costs would be much higher aswell).
The only problem was how to get the GitHub issues into Bitbucket. So here a little HowTo:
How To import GitHub issues into Bitbucket:
A cool guy from Cotonou made a Ruby script to export the GitHub issues in a format, Bitbucket is able to import:
https://github.com/sorich87/github-to-bitbucket-issues-migration
# Clone the repo
$ git clone https://github.com/sorich87/github-to-bitbucket-issues-migration.git issue-migrator
Cloning into ‚issue_migrator’…
remote: Counting objects: 40, done.
remote: Compressing objects: 100% (35/35), done.
remote: Total 40 (delta 4), reused 40 (delta 4)
Unpacking objects: 100% (40/40), done.
# cd into it
$ cd issue-migrator/
# install the packet ‚bundler‘ if not done
$ sudo apt-get install bundler
# Install dependencies listed in the gemfile
$ bundle install
Fetching gem metadata from https://rubygems.org/………
Fetching gem metadata from https://rubygems.org/..
Installing addressable (2.3.3)
Installing backports (3.1.1)
Installing multipart-post (1.2.0)
Installing faraday (0.8.7)
Installing faraday_middleware (0.9.0)
Installing hashie (2.0.3)
Installing json_pure (1.7.7)
Installing multi_json (1.7.2)
Installing netrc (0.7.7)
Installing octokit (1.24.0)
Installing rubyzip (0.9.9)
Using bundler (1.3.5)
Your bundle is complete!
Use bundle show [gemname] to see where a bundled gem is installed.
# Create the export by using following command
$ bundle exec ruby cli.rb [github_user]/[github_repo] [github_username] [github_password] exported-issues.zip
DONE!
An example for the last step would be:
$ bundle exec ruby cli.rb mammuth/repo1 mammuth 123password exported-issues.zip
I hope this helps you out!
