Skip to content

GitHub vs GitLab

Roger Xu edited this page May 4, 2016 · 1 revision

Resources

GitLab vs GitHub

Comparison

Branches

Item GitHub GitLab
Protected Branches X

Merge Requests

Item GitHub GitLab
Code Review X X
Required Status X
Merge Option X X

Issues

Item GitHub GitLab
Issue Template X X
Issue Vote X X
Attach Images X X
Attach Others X
Predefined Labels X
Task List X X
Ordered Task List X

Wiki

Item GitHub GitLab
Version Control X X
Multiple Formats X
Rename Page X
Writing Tools X
Attachments X
Task List X X

Snippets

Item GitHub GitLab
Private X X
Version Control X
Multiple Files X

1. Multiple authentication Levels

2. Group-level milestones

3. Attachments in issues

4. Innersourcing

5. Work-in-Progress Protection

Simply add 'WIP' to the title of a merge request to prevent anyone from merging it. This gives you all the code review power of merge requests, while protecting unfinished work.

6. Large open source projects

7. Powerful Issue Tracker

8. Search through Commits

GitLab not only allows you to search through code, but also searches through your commit messages.

9. Don't take our word for it.

Agilob contributed a great article about why you should choose GitLab for your next open source project.

Usage

Code Snippets

GitHub Gist

Posts

  • Draft - GitLab private wiki
  • Finalize - GitHub git-tips wiki
  • Publish - GitHub pages with images