Git vs GitHub

Need advice about which tool to choose?Ask the StackShare community!

Git

120.2K
95.8K
+ 1
6.6K
GitHub

165.2K
132.3K
+ 1
10.2K
Add tool

Git vs GitHub: What are the differences?

What is Git? Fast, scalable, distributed revision control system. Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

What is GitHub? Powerful collaboration, review, and code management for open source and private development projects. GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.

Git can be classified as a tool in the "Version Control System" category, while GitHub is grouped under "Code Collaboration & Version Control".

"Distributed version control system", "Efficient branching and merging" and "Fast" are the key factors why developers consider Git; whereas "Open source friendly", "Easy source control" and "Nice UI" are the primary reasons why GitHub is favored.

Git is an open source tool with 28.2K GitHub stars and 16.3K GitHub forks. Here's a link to Git's open source repository on GitHub.

According to the StackShare community, GitHub has a broader approval, being mentioned in 4714 company stacks & 6100 developers stacks; compared to Git, which is listed in 3934 company stacks and 4789 developer stacks.

Decisions about Git and GitHub
Weverton Timoteo

To communicate isn’t just getting rid of syntax errors and making code work. The code should communicate ideas to people through a programming language that computers can also understand.

You should adopt semantic variables, classes, modules, and methods names. For instance, in Ruby, we avoid using particular prefixes such as is_paid, get_name and set_name. In their places, we use directly paid?, name, and name=.

My advice is to use idiomatic and features that the programming language you use offers to you whenever possible, and figure out ways to better pass the message.

Why wouldn’t we be worried about semantics, typos, and styles? We should care for the quality of our code, and the many concepts that define it. You can start by using a linter to collect some issues from your codebase automatically.

See more
Weverton Timoteo

Do you review your Pull/Merge Request before assigning Reviewers?

If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:

  • Pick the correct target branch
  • Make Drafts explicit
  • Name things properly
  • Ask help for tools
  • Remove the noise
  • Fetch necessary data
  • Understand Mergeability
  • Pass the message
  • Add screenshots
  • Be found in the future
  • Comment inline in your changes

Read the blog post for more detailed explanation for each item :D

What else do you review before asking for code review?

See more
Weverton Timoteo

Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.

SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.

As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Git
Pros of GitHub
  • 1.4K
    Distributed version control system
  • 1.1K
    Efficient branching and merging
  • 964
    Fast
  • 846
    Open source
  • 728
    Better than svn
  • 367
    Great command-line application
  • 306
    Simple
  • 291
    Free
  • 232
    Easy to use
  • 222
    Does not require server
  • 27
    Distributed
  • 22
    Small & Fast
  • 18
    Feature based workflow
  • 15
    Staging Area
  • 13
    Most wide-spread VSC
  • 11
    Disposable Experimentation
  • 11
    Role-based codelines
  • 7
    Frictionless Context Switching
  • 6
    Data Assurance
  • 5
    Efficient
  • 4
    Just awesome
  • 3
    Easy branching and merging
  • 3
    Github integration
  • 2
    Flexible
  • 2
    Possible to lose history and commits
  • 1
    Rebase supported natively; reflog; access to plumbing
  • 1
    리속도가 빨라요
  • 1
    처리속도가 빨라요
  • 1
    Ys
  • 1
    Easy
  • 1
    Team Integration
  • 1
    Fast, scalable, distributed revision control system
  • 1
    Light
  • 1
    Flexible, easy, Safe, and fast
  • 1
    CLI is great, but the GUI tools are awesome
  • 1
    Compatible
  • 1
    It's what you do
  • 0
    Phinx
  • 1.8K
    Open source friendly
  • 1.5K
    Easy source control
  • 1.2K
    Nice UI
  • 1.1K
    Great for team collaboration
  • 857
    Easy setup
  • 496
    Issue tracker
  • 478
    Great community
  • 475
    Remote team collaboration
  • 444
    Great way to share
  • 436
    Pull request and features planning
  • 139
    Just works
  • 125
    Integrated in many tools
  • 112
    Free Public Repos
  • 106
    Github Gists
  • 103
    Github pages
  • 81
    Easy to find repos
  • 60
    Open source
  • 58
    Easy to find projects
  • 56
    Network effect
  • 55
    It's free
  • 47
    Extensive API
  • 42
    Organizations
  • 41
    Branching
  • 33
    Developer Profiles
  • 32
    Git Powered Wikis
  • 29
    Great for collaboration
  • 23
    It's fun
  • 22
    Community SDK involvement
  • 21
    Clean interface and good integrations
  • 19
    Learn from others source code
  • 14
    It integrates directly with Azure
  • 14
    Because: Git
  • 13
    Wide acceptance
  • 10
    Large community
  • 9
    Newsfeed
  • 9
    Standard in Open Source collab
  • 8
    It integrates directly with Hipchat
  • 7
    Beautiful user experience
  • 7
    Fast
  • 6
    Easy to discover new code libraries
  • 6
    Cloud SCM
  • 5
    Graphs
  • 5
    Smooth integration
  • 5
    Nice API
  • 5
    Integrations
  • 5
    It's awesome
  • 4
    Remarkable uptime
  • 4
    Hands down best online Git service available
  • 4
    Reliable
  • 3
    Easy to use and collaborate with others
  • 3
    CI Integration
  • 3
    Free HTML hosting
  • 3
    Loved by developers
  • 3
    Quick Onboarding
  • 3
    Security options
  • 3
    Simple but powerful
  • 3
    Uses GIT
  • 3
    Unlimited Public Repos at no cost
  • 3
    Version Control
  • 2
    Nice to use
  • 1
    Free private repos
  • 1
    Easy deployment via SSH
  • 1
    Beautiful
  • 1
    Owned by micrcosoft
  • 1
    Free HTML hostings
  • 1
    Self Hosted
  • 1
    All in one development service
  • 1
    Easy to use
  • 1
    Good tools support
  • 1
    Easy source control and everything is backed up
  • 1
    Leads the copycats
  • 1
    Never dethroned
  • 1
    Ci
  • 1
    Issues tracker
  • 1
    Easy and efficient maintainance of the projects
  • 1
    IAM
  • 1
    IAM integration
  • 0
    Profound
  • 0
    1

Sign up to add or upvote prosMake informed product decisions

Cons of Git
Cons of GitHub
  • 16
    Hard to learn
  • 11
    Inconsistent command line interface
  • 9
    Easy to lose uncommitted work
  • 7
    Worst documentation ever possibly made
  • 5
    Awful merge handling
  • 3
    Unexistent preventive security flows
  • 3
    Rebase hell
  • 2
    When --force is disabled, cannot rebase
  • 2
    Ironically even die-hard supporters screw up badly
  • 45
    Owned by micrcosoft
  • 36
    Expensive for lone developers that want private repos
  • 15
    Relatively slow product/feature release cadence
  • 10
    API scoping could be better
  • 8
    Only 3 collaborators for private repos
  • 3
    Limited featureset for issue management
  • 2
    GitHub Packages does not support SNAPSHOT versions
  • 1
    Have to use a token for the package registry
  • 1
    No multilingual interface
  • 1
    Takes a long time to commit

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is Git?

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

What is GitHub?

GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Git?
What companies use GitHub?
See which teams inside your own company are using Git or GitHub.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Git?
What tools integrate with GitHub?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Mar 24 2021 at 12:57PM

Pinterest

+7
3
1441
Dec 8 2020 at 5:50PM

DigitalOcean

+11
2
1707
+4
4
1692
+2
2
1007
+3
2
970
+3
6
897
Mar 18 2020 at 9:12AM

LaunchDarkly

+2
6
902
What are some alternatives to Git and GitHub?
SVN (Subversion)
Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations.
Bitbucket
Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
Perforce
Visibility, access control, workflow and code management for Git environments. Flexibility of collaborating on the same codebase and code reviews using any combination of Perforce and Git workflows and tools without compromise.
Mercurial
Mercurial is dedicated to speed and efficiency with a sane user interface. It is written in Python. Mercurial's implementation and data structures are designed to be fast. You can generate diffs between revisions, or jump back in time within seconds.
GitLab
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
See all alternatives
Reviews of Git and GitHub
Staff Software Engineer
Review of
GitHub

For starters you can fork a repo, edit it online and send a pull request which is huge if its something very small that you want to commit. The whole pull request system, the UI and the UX are great. If I sent out a pull request that failed on travis CI then all I need to do is fix it in my fork and the original pull request will have these updates as well making it super easy for everyone involved. Overall a great service.

Review of
GitHub

I love GitHub! They provide a completely free service for hosting, storing, and collaborating on code. Seriously, if you aren't using them, go sign up now.

Review of
GitHub

Great collaboration-friendly git repository hosting. Plus integration with all sorts of other stuff, like Travis CI. But the command bar has disappeared...

Science
Review of
GitHub

It's the best tools I have ever used.

How developers use Git and GitHub
Airbnb uses
GitHub

"Having a CI server building all commits across all branches was a huge first step, but to make this useful we needed to surface the outcome of these builds. This is where GitHub’s commit status API comes in. Every time our CI server begins a build, it pings GitHub’s commit status endpoint, and every time it completes a build it hits the endpoint again with the outcome. Now every open PR includes a yellow/red/green indicator for the branch in question, with a direct link to the build status page on our CI server. In practice this means more transparency, faster feedback cycles, and a guarantee that every branch merged into master has a passing test suite. This integration has been a huge help in keeping our master branch green, and has thus greatly reduced our deploy times (since engineers aren’t waiting on build failures to be resolved in master)."

yaswanthgoud3235 uses
GitHub

GitHub is a Web-based Git version control repository hosting service. It is mostly used for computer code. It offers all of the distributed version control and source code management (SCM) functionality of Git as well as adding its own features. It provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project

Instacart uses
GitHub

Yeah, so we use GitHub, and we basically use a variant of continuous deployment where when anyone merges in a feature that they’ve finished with, they ship it immediately, and we bundle it up as a build pack and send it to all of our EC2 servers... Any developer on the team can trigger a build and deploy at any time. So on a given day, we probably deploy 20 or 30 times to prod.

StackShare uses
GitHub

One thing I really wish GitHub had: Trello-style kanban for Issues. There are a bunch of services and tools that add Kanban to GitHub Issues. But Trello just seems far better. If GitHub had it’s own kanban tool, I’d probably use it. Right now it’s pretty painful to try to tie cards to commits manually (when/if we remember to).

shridhardalavi uses
GitHub

GitHub is a web-based hosting service for version control using Git. It offers all of the distributed version control and source code management (SCM) functionality of Git as well as adding its own features. It provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project.

papaver uses
Git

been an avid git user for over 6 years. was a little hard to grasp coming from the world of perforce but once it hit me that it was just a glorified patch manager everything fell into place. mainly use the command line interface, most ui's feel bulky and weak.

Scrayos UG (haftungsbeschränkt) uses
Git

Git has rendered itself to be an integral part of all development at JustChunks. We heavily rely on Git as our version-control-system of choice and use branches, tags and decentralized-development to achieve our software-management-goals.

Jonathan Bro uses
Git

I use Git because there is nothing else that seems better for backup and working with other developers. However, the learning curve is high and there are times when non-developers must also know how to use git.

Mountain Stream Software uses
Git

the next generation of version control, all others follow older outdated models. Open Source, no fees to use. Can hoist up your own internal server. Can live on a thumb drive. Developers can share from any OS.

Eldoria uses
Git

Git ist ein essentieller Bestandteil unserer Entwicklungsteams. Sei es zur Versionskontrolle, Backupen von Code, dem gemeinsamen arbeiten an Projekten. Durch Git Flow haben wir eine effektive Arbeitsweise.