Hacker News Reader

Comment by flashm | Hacker News Reader

I've moved all my private repos to Gitlab based on the chat on here and other places recently RE Github, Gitlab, and other solutions.

I'm very happy overall, the interface is great. It's a bit slower than github currently (the web interface) as I'm using the online version rather than self hosted, but apart from that it's really bloody good.

I'll be recommending it to others going forward and using it for all new repos that I want hosted.

View on HN

Thanks, that's good to hear.

We're working hard on making it faster, this release being a major milestone in that work.

Last release, we started shipping a performance monitoring tool [0], to make it easier to see what exactly is slow.

[0]: https://about.gitlab.com/2016/01/22/gitlab-8-4-released/

Nice, I'll take a look.

Yep, also see our 'Make GitLab.com fast again' issue https://gitlab.com/gitlab-com/operations/issues/42 for updates about performance.

What procedures did you follow to move your private repos over? I have been using private, self hosted git for years now. Were you able to move things over and keep commit history? (since I guess that's the only feature I currently have.)

If you move your repository by importing it (in GitLab UI, under new project) or just by clone + pushing it yourself, you will always retain your entire commit history.

Is there an issue/PR migration path as well?

If you use our GitHub importer, it will migrate your code, wiki, issues and PRs. It can do it in batch for all your GH projects.

Docs here: http://doc.gitlab.com/ce/workflow/importing/import_projects_...

If you import from GitHub, your issues, PRs, wiki and all code will be imported.

It would be really cool if GitHub stored issue, PR, and wiki information in the main Git repo. That way all of these things would be very easy to keep in sync across different services.

I've had this idea for a while now. I wonder if it would be practical and if anyone has ever tried something like this.

That's what Joey Hess' github-backup does: https://github.com/joeyh/github-backup

It's one way, though, you can't create a new Issue or PR by just updating repo.

As a separate root branch, it would work nicely. There are huge benefits also in that you get an inspectable history of issues. From GitHub's perspective, it would be more difficult to authenticate issue changes—they'd need signed commits and pre push validation, right?

That would be cool, we're discussing distributed code review and issues in https://gitlab.com/gitlab-org/gitlab-ce/issues/4084

I just added Gitlab as a new remote, and pushed. Easy as that. Keeps the entire repo history. I then just removed my old Github remotes.

Thank git for a model that 'allow' migration through a primitive operation.

Apart from the other methods mentioned here (such as the import from the user interface http://doc.gitlab.com/ce/workflow/importing/README.html) is also an import rake task http://doc.gitlab.com/ce/raketasks/import.html for administrators.

I guess it's good if you just want private stuff, but if you want to build portfolio type thing or want discoverability private stuff isn't ideal

No problem, just click the "Public" radio button.

Reply on news.ycombinator.com