What we hear most frequently a reason for switching is the in the integrated CI, CD, and container registry. The GitHub importer will import your repo, issues, PRs, milestones, labels, and wikis http://docs.gitlab.com/ce/workflow/importing/import_projects...
Ask HN: GitHub vs. Gitlab?
11–20 of 113 posts
Re: Ask HN: GitHub vs. Gitlab?
#12Re: Ask HN: GitHub vs. Gitlab?
#13I moved most of new private repos to gitlab.com from bitbucket. It's nice to experience interface parity between self hosted and public gitlab. And more and more of my clients move to self hosted gitlab as well.
Re: Ask HN: GitHub vs. Gitlab?
#14I have not really tried GitLab's hosted offering, I have a couple repos up there, but nothing extensive.
Have you considered a VPS with Gogs? It's super lightweight and easier than snot to setup.
Re: Ask HN: GitHub vs. Gitlab?
#15$7 for a GitHub account with unlimited private projects is a pretty good deal, especially compared to their previous pricing tiers. I also think the experience of using one website for most open source projects as well as private projects is better.
Re: Ask HN: GitHub vs. Gitlab?
#16Re: Ask HN: GitHub vs. Gitlab?
#17Gitlab's servers have been slow in my experience. Sometimes taking 10-15 seconds to push up a new commit. I got tired of waiting and moved everything back to bitbucket. Both gitlab and bitbuckets source code browsing is slow and a little clunky. GitHub's source code browsing is definitely the best.
We solved most of the time waiting when pushing a new commit, see the API timings slide on https://www.scribd.com/doc/316471059/GitLab-Infrastructure-2...
The web interface is still slower than we like. We've doubled the team of performance engineers and we're making progress, see https://gitlab.com/gitlab-com/infrastructure/issues/59 and all issues labeled with performance https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&sor...
Re: Ask HN: GitHub vs. Gitlab?
#18Re: Ask HN: GitHub vs. Gitlab?
#19Re: Ask HN: GitHub vs. Gitlab?
#20I am contemplating a move from Github to Gitlab right now. Feature-wise there seems to be enough parity with Github to make this sort of thing possible. Also, gitlab's CI system is attractive and being able to run our own runners in our own environment (we currently used an outsourced CI system.) We're also doing it because Github enterprise is too expensive, and we want to rely on less external dependencies in our e…