Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to Migrate a Git Repository from GitHub to Bitbucket

bluelabellabs.com

Post reply on HN
Print view View original

11–20 of 53 posts

Re: How to Migrate a Git Repository from GitHub to Bitbucket

#11

Post by dmkirwan »

xtracto wrote: post #8
forgotpwd16 wrote: post #6

There isn't anything GitHub or/and Bitbucket specific to this. That's just the procedure to copy (clone/push) a repo from one Git server to another. What about issues, PRs, actions, wiki, ...? GitHub isn't only used to host the code alone.

Right. At a previous place we migrated from Github to Gitlab, but we have to keep the GH repo for the merge request, approvals and paper trial. This for PCI and SOC2 auditing.

That's interesting. Was Github Enterprise too expensive or was there another reason you didn't use it? What advantage did partially moving to Gitlab bring? This question is coming from a genuine place of curiosity, in case that's not coming across via text.

Re: How to Migrate a Git Repository from GitHub to Bitbucket

#13

Post by jackcviers3 »

dmkirwan wrote: post #9

Ethical concerns aside*, I far preferred Github to BitBucket. Bitbucket has been incredibly unstable for the last few years that I've been using it at work. I regularly see the "We're experiencing issues..." banner when I review pull requests. We don't use bitbucket pipelines, but they seem to be the most unstable part of the product. I haven't used Gitlab in years so I can't give any up-to-date commentary on that as…

Huh. Been using it for the last 5 years with pipelines over the last year and had no issues. The pipelines do require weird strategies for big scala compiles though.

Re: How to Migrate a Git Repository from GitHub to Bitbucket

#14

Post by igetspam »

xtracto wrote: post #8
forgotpwd16 wrote: post #6

There isn't anything GitHub or/and Bitbucket specific to this. That's just the procedure to copy (clone/push) a repo from one Git server to another. What about issues, PRs, actions, wiki, ...? GitHub isn't only used to host the code alone.

Right. At a previous place we migrated from Github to Gitlab, but we have to keep the GH repo for the merge request, approvals and paper trial. This for PCI and SOC2 auditing.

Someone didn't understand compliance. To have painted yourself into that tight of a corner is just bad policy. I've been involved in half a dozen SOC2 programs and can't imagine how I'd actually be able to create that problem.

Re: How to Migrate a Git Repository from GitHub to Bitbucket

#15

Post by jackcviers3 »

igetspam wrote: post #12

Step 1: Don't The only thing bitbucket has going for it is that it's the same biller as all the other mediocre software you're using most days. It's pretty awful.

It was cheaper for private repositories (free for teams less than 5) for a long time. I think Gitlab is cheaper now.

Re: How to Migrate a Git Repository from GitHub to Bitbucket

#17

Post by gethub »

coding123 wrote: post #7
gethub wrote: post #3

Earlier quoted context omitted.

Amen. GitLab: every thing but each thing is just okay GitHub: some things but each thing is great Bitbucket: some things but each is just okay

GL is pretty great at the following: cost, permissions and CICD.

The pricing has changed recently, grandfathered in organisations have reasonable pricing (relative to GitHub) but the pricing for new organisations is much more expensive than GitHub. You can compare GitLab on features, but if you want to use those features the pricing is not comparable (GitLab's $100/user/m vs. GitHub's $21/user/m).

https://about.gitlab.com/blog/2021/01/26/new-gitlab-product-...

Re: How to Migrate a Git Repository from GitHub to Bitbucket

#18

Post by callmeal »

I don't know if somethings going on, but the last couple of weeks, Bitbucket has been incredibly slow, with pull request merges taking minutes for a tiny (
  This pull request is being merged in the background. This typically only takes a few seconds but may take longer. You can safely navigate away.
banner is now completely familiar to our dev team. I've seen the merge sometimes randomly fail (refreshing that screen causes the "Merge" button to reappear and the pull request state showing as "Open".

Re: How to Migrate a Git Repository from GitHub to Bitbucket

#19

Post by gtirloni »

callmeal wrote: post #18

I don't know if somethings going on, but the last couple of weeks, Bitbucket has been incredibly slow, with pull request merges taking minutes for a tiny ( This pull request is being merged in the background. This typically only takes a few seconds but may take longer. You can safely navigate away. banner is now completely familiar to our dev team. I've seen the merge sometimes randomly fail (refreshing that screen c…

It's always been like that, in my experience.

Re: How to Migrate a Git Repository from GitHub to Bitbucket

#20

Post by gtirloni »

dmkirwan wrote: post #9

Ethical concerns aside*, I far preferred Github to BitBucket. Bitbucket has been incredibly unstable for the last few years that I've been using it at work. I regularly see the "We're experiencing issues..." banner when I review pull requests. We don't use bitbucket pipelines, but they seem to be the most unstable part of the product. I haven't used Gitlab in years so I can't give any up-to-date commentary on that as…

What's unethical about GitHub?
Post reply on HN