GitHub vs Gitter: What are the differences?
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.
What is Gitter? Messaging for people who make software. Integrated with your team, projects and your code. Free chat rooms for your public repositories A bit like IRC only smarter. Chats for private repositories as well as organisations..
GitHub can be classified as a tool in the "Code Collaboration & Version Control" category, while Gitter is grouped under "Group Chat & Notifications".
Some of the features offered by GitHub are:
- Command Instructions
- Source Browser
- Git Powered Wikis
On the other hand, Gitter provides the following key features:
- Know who's seen any message
- Edit messages after you've sent them
- Full emoji support
"Open source friendly" is the primary reason why developers consider GitHub over the competitors, whereas "Github integration" was stated as the key factor in picking Gitter.
According to the StackShare community, GitHub has a broader approval, being mentioned in 4714 company stacks & 6099 developers stacks; compared to Gitter, which is listed in 25 company stacks and 41 developer stacks.
What is GitHub?
What is Gitter?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Gitter?
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I find I really like using GitHub because its issue tracker integrates really well into my project flow and the projects feature allows me to organize different efforts into boards. The automation features allow my issues to automatically progress through some states on the boards when I merge pull requests.
My Python / Django app is deployed on Heroku with PostgreSQL database and uWSGI webserver.
Keep with GitHub if you feel comfortable, If you want to switch to other keep in mind the change of mindset and you will need time to adapt, i'm not saying that GitLab is bad or difficult just the opposite, but it can be overwhelming because it have more integrated features (I love this) than GitHub , what it means more configs available that you can mess up.
I use GitHub because it can handle all the project management (it's got a great built-in kanban for projects that integrate beautifully with Issues. Also line-comments on commits are super useful to us. The integrated environment is perfect, light-weight, and it's nice NOT to have to deal w/ project management with a tool like Trello outside of the codebase. It's good to have everything in one place.
I use GitHub because since it was bought by Microsoft, some new features are being introduced in and most importantly, the git clone speed is usually much faster than gitlab. Gitlab is very good, I like the member permission function which is good for collaborative coding. But still I am more used to github interface.
I prefer to use GitHub because their website speed is faster and the availability more reliable than the competitors, this is our top priority as GitHub is our core functionality we need to be able to operate in development. And since their new pricing make more sense and work for us as they are charging based on how many developers than repositories, this help us to keep our repositories smaller by dividing each codebase into specifics repositories.
How we ended up choosing Confluence as our internal web / wiki / documentation platform at Katana.
It happened because we chose Bitbucket over GitHub . We had Katana's first hackaton to assemble and test product engineering platform. It turned out that at that time you could have Bitbucket's private repositories and a team of five people for free - Done!
This decision led us to using Bitbucket pipelines for CI, Jira for Kanban, and finally, Confluence. We also use Microsoft Office 365 and started with using OneNote, but SharePoint is still a nightmare product to use to collaborate, so OneNote had to go.
Now, when thinking of the key value of Confluence to Katana then it is Product Requirements Management. We use Page Properties macros, integrations (with Slack , InVision, Sketch etc.) to manage Product Roadmap, flash out Epic and User Stories.
We ended up with using Confluence because it is the best fit for our current engineering ecosystem.
We use GitHub because it's the default go-to place for the Free software community. Currently, Github is enjoying the network effect: you write code there because everyone writes there code there, so this choice was less of a choice than "what we all end up doing".
Personally, I prefer GitLab for its bundled-in tools like CI, boards, packaging, and Docker repo, but so long as the vast majority of talented nerds out there are on Github, that's where Paperless will be.
I use GitHub because it's the coolest kid on the block for open source. Searching for repos you need/want is easy.
Especially with the apache foundation moving their workloads to them, unlimited private repos, and a package registry on the way, they are becoming the one stop shop for open source needs.
I'm curious to see how the GitHub Sponsors(patreon for developers) plays out, and what it'll do for open source. Hopefully, they design it in a way where it's not abused by big tech to "plant" developers that look like they're building open source when they're actually building proprietary tools.
We're using Git through GitHub for public repositories and GitLab for our private repositories due to its easy to use features. Docker and Kubernetes are a must have for our highly scalable infrastructure complimented by HAProxy with Varnish in front of it. We are using a lot of npm and Visual Studio Code in our development sessions.
The world we currently live in consists of Jargon technologies and with each passing day a new technology is introduced in the market which serves to improves the life in one or the other way. #Github is one of the splendid Version Control repository management services which has a key component in the software development workflow and has a greater impact on developers life giving valuable essence to utilize the best tools fitted for any product.
In the last few years, GitHub and GitLab positioned themselves as handy assistants for developers, particularly when working in large teams. I use GitHub because it has overcome my time in maintaining code and product #Repositories. #GitHubPullRequests along side with #GithubIssues have helped me and many moderators like me to keep a track of the #commits done by any number of people around the world.
People synchronization to various roots of our project repositories has made our product to stand Safe Secure Accessible and #Feasible The newer addition to #GithubMarket and #ToolsForGithub has helped our community to use various in-built applications which provided us to track up with #Documentation, #Licensing #Codebase-Hosting and #DependencyMonitoring
A bit difference in GitHub and GitLab though both are Version Control repository management services which provides key component in the software development workflow. A decision of choosing GitHub over GitLab is major leap extension from code management, to deployment and monitoring alongside looking beyond the code base hosting provided best fitted tools for developer communities.
- Authentication stages - With GitLab you can set and modify people’s permissions according to their role. In GitHub, you can decide if someone gets a read or write access to a repository.
- Built-In Continuous Integrations - GitLab offers its very own CI for free. No need to use an external CI service. And if you are already used to an external CI, you can obviously integrate with Jenkins, etc whereas GitHub offers various 3rd party integrations – such as Travis CI, CircleCI or Codeship – for running and testing your code. However, there’s no built-in CI solution at the moment.
- Import/Export Resources - GitLab offers detailed documentation on how to import your data from other vendors – such as GitHub, Bitbucket to GitLab. GitHub, on the other hand, does not offer such detailed documentation for the most common git repositories. However, GitHub offers to use GitHub Importer if you have your source code in Subversion, Mercurial, TFS and others.
Also when it comes to exporting data, GitLab seems to do a pretty solid job, offering you the ability to export your projects including the following data:
- Wiki and project repositories
- Project uploads
- The configuration including webhooks and services
- Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities.
GitHub, on the other hand, seems to be more restrictive when it comes to export features of existing GitHub repositories. * Integrations - #githubmarketplace gives you an essence to have multiple and competitive integrations whereas you will find less in the GitLab.
So go ahead with better understanding.
We run a major community project named as @Donut which is an #OpenSource social platform which allows communities to set up their own social environment and @slack platform drives us through the best experience of community interaction. Though we have been using some Open Source Interacting platforms like Gitter and Zulip but the fact that Slack exists and is such an essential tool, it’s really helped us with scaling and still feeling connected to one another across remote places with various teams with appropriate features in it.
The #User-Friendly Slack brings all the organised conversations at one place giving a prospectus to feel the better user experience on desktop.
Followings its pros:
- Allow creating of various channels which can be best suited to organised #projects, #teams and #events.
- Allow multiple tools and integrations such as Google Drive and GitHub
- Video Conferencing addition helps teams to organise meetings.
- No limit for addition of users and its free.
- Allow threads to keep side conversations from derailing the topic or project at hand.
The most crucial thing it supports the best security and protection with 2 factors authentication.
This is my stack in Application & Data
My Utilities Tools
Google Analytics Postman Elasticsearch
My Devops Tools
Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack
My Business Tools
When you interact with CircleCI's web application, all of your requests are hitting the #API hosts. We handle the majority of our authentication via #OAuth from GitHub or Bitbucket. We provide programmatic access to everything exposed in the UI through an API token that you can generate once you have authenticated.
From a StackShare Community member: “We’re about to start a chat group for our open source project (over 5K stars on GitHub) so we can let our community collaborate more closely. The obvious choice would be Slack (k8s and a ton of major projects use it), but we’ve seen Gitter (webpack uses it) for a lot of open source projects, Discord (Vue.js moved to them), and as of late I’m seeing Spectrum more and more often. Does anyone have experience with these or other alternatives? Is it even worth assessing all these options, or should we just go with Slack? Some things that are important to us: free, all the regular integrations (GitHub, Heroku, etc), mobile & desktop apps, and open source is of course a plus."
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.
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.
Great collaboration-friendly git repository hosting. Plus integration with all sorts of other stuff, like Travis CI. But the command bar has disappeared...
It's the best tools I have ever used.
"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)."
Pervasive, easy to use Git repo hosting. I host ongoing personal projects privately and my personal blog (via GitHub Pages).
I also take successful proofs of concept (for example, experimenting with linking AWS Lambda to Heroku Postgres to create a serverless SQL backed web app), and host them as public example repos. These are linked to Dependabot and CircleCI if they have tests so that dependencies can be kept up to date automatically over time and the code using the dependencies can stay fresh over time for example viewers.
We haven't found a better way to communicate directly with the core contributors and developers for many open source projects we utilize on GitHub (Scala, Scala-js, Sinatra, Apache top-level projects, just to name a few).
It is a solid piece of software that appeals to us who have used Slack in the past, and the tight integration with a single GitHub repository or organization for each Gitter room just makes sense in our eyes.
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
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.
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).
Many GitHub communities are on Gitter. It's a great place to ask and answer questions related to open-source frameworks and libraries.
Using Gitter for open source talks and directly communicating with contributors.