In contrast to GitLab, there are free repositories on GitHub. This has led to an unfortunate side effect. Significant libraries and modules, packages and whole frameworks are related to especial user profiles. Even if a person hasn't any relation to project services. However, GitHub drew attention to this disadvantage and started to improve the functionality of organizations and commands. There are commands exist in repositories now, you can create subgroups and indicate your personal settings and access to repositories.
Free private command repositories make a lot of companies to select GitLab frequently. But the functional "subgroups" are unavailable to private accounts. Therefore, Gitlab groups became more important than personal accounts. Many developers call groups by their nicknames and add underscore to identify an account name.
Conversely, GitHub supports for a long time an idea that significant work in programming is done separately by different people. Encouraging "awards" (stars, commits) have to be stored in a user's "private office". It resulted in GitHub public activity that's taken into account in recruiting, conferences, etc. What can you store on GitLab?
In addition to web-service, GitLab provides an open-source code. The system can be launched fast and painless on its server. You can use the web-server for such tasks:
GitHub is for everything else
- Closed content for teams, companies, organizations.
- Personal working repositories (to store as a precaution).
- Personal user data.
- Training material projects.
- Web-development (suitable tool - GitLab Pages).
All other content can be confidently directed to GitHub. If you want to allow other users to get access to use it and invoke it. Links on GitHub repositories inspire trust more than GitLab and will be viewed more frequently. Public activity and projects can help you to make a portfolio that can make you get a job.