Git vs GitHub

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

Git

154.9K
129.4K
+ 1
6.6K
GitHub

213.2K
178.6K
+ 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
Weverton Timoteo

One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but git rebase -i is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.

It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.

See more
Kamaleshwar BN
Senior Software Engineer at Pulley · | 8 upvotes · 424.7K views

Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.

See more

Gitlab as A LOT of features that GitHub and Azure DevOps are missing. Even if both GH and Azure are backed by Microsoft, GitLab being open source has a faster upgrade rate and the hosted by gitlab.com solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!

See more

(1/2) In terms of DevOps we chose GitHub, Git, Visual Studio Code, Sentry, Yarn, CircleCI.

  • GitHub was chosen because of its features such as GitHub Projects, GitHub Issues, and GitHub Milestones, which are normally separate tools such as Trello for issue tracking, but come as part a package with GitHub. This choice is also influenced by our decision for using Git for version control.

  • Git was chosen as our version control because of the wide popularity, familiarity in our team, and rich list of tools that support integrations. A tool such as Perforce does not suit our needs because we do not require the mapping features important to huge code bases and the lack of many popular integrations is not appealing.

  • Visual Studio Code was chosen as our primary source-code editor for an array of reasons. VS code works well with our chosen version control system since it comes with embedded Git control out of the box. For every language or framework that we are working in, there are multiple extensions to improve our team's productivity and efficiency. It also has live collaboration through their LiveShare feature and more, all while maintaining itself as a lightweight tool.

  • Sentry, Yarn, andCircleCI in part 2.

See more
YUVRENDER GILL

We will use the ubiquitous combination of Git for version control and GitHub for code hosting. They have all the functionality we require for this project and will fit perfectly into our development workflow with up to three developers working simultaneously on the codebase. We also plan on using GitHub Actions to set up our CI/CD workflows.

VS Code will be our primary code editor due to its combination of developer-friendly features, including a large extensions library, IntelliSense code completion, Git integration, and powerful debugging tools. Furthermore, it offers better performance and more simplicity than full-fledged IDEs while supporting a multitude of languages.

Selenium will be used to perform automated testing of our web application. It supports all major web browsers and operating systems and supports test scripts to be written in multiple languages, including Python which we are also planning to use for our back-end, helping us to consolidate the languages required for our project. In addition, Selenium is free and has support for most CI/CD tools.

See more
Nazar Atamaniuk
Shared insights
on
DeployPlaceDeployPlaceGitHubGitHubGitLabGitLab

At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I can’t imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesn’t let us chose it for our projects.

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
  • 960
    Fast
  • 845
    Open source
  • 728
    Better than svn
  • 368
    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
    Possible to lose history and commits
  • 2
    Compatible
  • 2
    Flexible
  • 1
    Team Integration
  • 1
    Light
  • 1
    Easy
  • 1
    Fast, scalable, distributed revision control system
  • 1
    Rebase supported natively; reflog; access to plumbing
  • 1
    Flexible, easy, Safe, and fast
  • 1
    CLI is great, but the GUI tools are awesome
  • 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
  • 863
    Easy setup
  • 502
    Issue tracker
  • 484
    Great community
  • 480
    Remote team collaboration
  • 448
    Great way to share
  • 441
    Pull request and features planning
  • 144
    Just works
  • 131
    Integrated in many tools
  • 117
    Free Public Repos
  • 112
    Github Gists
  • 108
    Github pages
  • 81
    Easy to find repos
  • 61
    Open source
  • 58
    It's free
  • 58
    Easy to find projects
  • 56
    Network effect
  • 48
    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
  • 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
    Nice API
  • 5
    Smooth integration
  • 5
    Graphs
  • 5
    It's awesome
  • 5
    Integrations
  • 4
    Hands down best online Git service available
  • 4
    Reliable
  • 4
    Remarkable uptime
  • 3
    Quick Onboarding
  • 3
    CI Integration
  • 3
    Easy to use and collaborate with others
  • 3
    Version Control
  • 3
    Unlimited Public Repos at no cost
  • 3
    Free HTML hosting
  • 3
    Loved by developers
  • 3
    Uses GIT
  • 3
    Simple but powerful
  • 3
    Security options
  • 2
    Nice to use
  • 1
    Ci
  • 1
    Very Easy to Use
  • 1
    Free private repos
  • 1
    Good tools support
  • 1
    Owned by micrcosoft
  • 1
    All in one development service
  • 1
    Easy to use
  • 1
    Easy deployment via SSH
  • 1
    IAM
  • 1
    IAM integration
  • 1
    Issues tracker
  • 1
    Easy source control and everything is backed up
  • 1
    Leads the copycats
  • 1
    Never dethroned
  • 1
    Easy and efficient maintainance of the projects
  • 1
    Beautiful
  • 1
    Free HTML hostings
  • 1
    Self Hosted
  • 0
    1
  • 0
    Profound

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
  • 49
    Owned by micrcosoft
  • 37
    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
  • 2
    Does not have a graph for showing history like git lens
  • 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

GitJenkinsKafka+7
3
1758
Dec 8 2020 at 5:50PM

DigitalOcean

GitHubMySQLPostgreSQL+11
2
2070
GitJenkinsGroovy+4
4
1905
GitCloudBees+2
3
3199
GitHubOptimizelySegment+3
2
1070
Git.NETCloudBees+3
6
964
Mar 18 2020 at 9:12AM

LaunchDarkly

GitHubLaunchDarkly+2
6
1011
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