Our local GitLab setup is rather recent and isn't quite a critical part of our infrastructure just yet, but I anticipate over the next few months we'll be switching more and more over to it. I recently started on a brand new project which is currently hosted on GitLab, though it'll probably move to public GitHub after we get approval to release it under a Free Software licence.
These limitations are becoming more painful as we grow our team, and deal with more issues across more repos.
Gitlab seems to be iterating pretty quickly. Github glacially.
For us, the killer feature that Github has is the network effect. We want to make it as easy for people to contribute code/collaborate on Grafana, and Github is where all the action (developers and code) is.
I suspect that many medium/large OSS projects have the same mindset.
I understand if you don't move to GitLab yet because of the network effect. Just so you know, GitLab allows people to log in with their GitHub account.
It's arguably even harder for small projects to switch to Gitlab -- Github is the main way people discover us. That's where people are looking.
While I continue to host public projects on Github, my key reasons to host other projects on Gitlab are privacy, security, control, and availability. Pre-commit hooks (that can reject code) are awesome.
You can still login with github or bitbucket, and there is a 'migrate project from ["github","bitbucket"], so, why not?
it even moves your issues over and such.
I did lose milstones on a few of my projects (where I used them) though.
I'm hoping this can reduce some cost since i'm currently spending a lot on Github and Travis CI.