GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
$4
per month per user
Google Workspace
Score 9.1 out of 10
N/A
Google Workspace enables teams of all sizes to connect, create and collaborate. It includes productivity and collaboration tools for work: Gmail for custom business email, Drive for cloud storage, Docs for word processing, Meet for video and voice conferencing, Chat for team messaging, Slides for presentation building, and shared Calendars.
Git is my favorite among all of the version control systems out there. It follows the Linux software philosophy of being built by many loosely coupled and small components that do one thing well. It's incredibly open, and its adoption in the open source community seems to be …
For us, we use both Git and GitHub so they were a package. I suppose you could use Git with another VCS/hosting service to track changes if it fit well enough, but for us we just went with design out of the box. We pay for the GitHub private repository for the extra security.
There are not many surviving alternatives for Git (maybe SVN) which in itself is quite meaningful. Git is the best versioning system of all time for programming, period. The difference between a good mathematical tool and sending .zip-s around emailing lists or FTP drives is so …
Git is the best Source Control Management Tool I've used. Every company, team, and project I've worked on professionally either used Git 100%, or was moving to Git, away from the alternatives like SVN. Git has all the features necessary, as well as a very large community of …
After using Subversion previously for a number of years, Git comes across as the new and improved source control approach. Git seems very suited to working with Agile:- branches can be created easily, allowing multiple developers to switch to them quickly, and having local …
GitHub is the ONLY version control system I've ever used. I used it from day 1 at Dev Bootcamp since they make a pretty big push for all students to learn git as a language and to use GitHub for version control. It is difficult to say how GitHub stacks up against the rest of …
Bitbucket has an interface that is much uglier and much more confusing to use. The learning curve is therefore much greater with Bitbucket. However, Bitbucket allows for free private repositories for small teams, which is a huge plus, and if your team is small enough, that …
GitHub holds up well against Gitlab and Bitbucket in terms of ease of use, documentation, support, and features for enterprise. However, it falls a bit flat on the pricing side with paid plans for private repos. It has been and remains the service of choice on which to post …
In my opinion, GitHub beats all of the competition.
The other services offer some things that could be considered benefits in some scenarios: Bitbucket has good integration with other Atlassian products, Gitlab is self-hosted and completely free, Beanstalk integrates with some …
Git and GitHub are so much easier to use. I didn't necessarily find the others that I've tried difficult, but they all had their quirks. GitHub has their quirks, but their quirks make sense once you really think about i. The other may or may not have command line options, …
The most direct competitor to GitHub that I can think of would be BitBucket from Atlassian. The biggest advantage that I know of for BitBucket would be that they support both git and Mercurial. If you have at least one team or project using Mercurial, then BitBucket would be …
Github and git, in general, is much better than SVN or Subversion for version tracking and code collaboration. It takes the best parts of SVN and fixes a lot of what was broken with it. Github's own UI has evolved really well over time and they have taken developer productivity …
We picked GitHub because it's what I was most familiar with when we started. We're testing out self-hosted Gitlab because it not only handles all the features we're using on GitHub, but it also has a continuous integration service which is currently implemented by a third party …
GitHub is the best git repository service available and the industry standard. It's fast, reliable, and constantly adding new services. Bitbucket and Gitlab are both good, free (or inexpensive) alternatives, but they lack some of the design and speed of GitHub. Both alternative …
Github has a much larger community of users than Gitlab, and its interface is slightly more 'clean' and easy to navigate. Github's brand name is also more recognizable and its users are generally very helpful and willing to contribute to exciting open source projects.
Along with Github, I've used Bitbucket and Gitlab. Bitbucket integrates with FishEye, which allows you to institute Code Reviews and create a viable merge process. Gitlab offers similar built in tools. With Github, I'm not aware of any similar features, but this is likely due …
I prefer GitHub on a personal level because it is free for personal use. It allows me to work on things with friends, or have easy access to open source software because of this.
[We selected GitHub because] It can easily integrate with different IDEs like Eclipse, Intellij and many more. Can fork and commit without any disturbance in the team; code conflicts can be easily resolved. Can easily monitor the changes made and revert if any bugs were …
Microsoft Team Foundation Server was too heavy and too complex for fast dvelopment. The integration with opensource build solutions (i.e jenkins) was not explored but the main feedback on this tool was its complexity. CVS and SVN used to be standards in past years and fit …
It's way easier to use and integrate with other applications as it was the first application that was created. Even though, I feel there has to be improvements on how to handle the branching in Github, with constant use I feel pretty much comfortable.
Atlassian's Bitbucket and SourceTree products are Git compatible and in our opinion offer a more intelligible and well-organized UI. These products integrate with JIRA for project management, but these features come at a higher monetary cost than GitHub.
GitHub is the only Git Repository tool I have extensive experience with. As a free solution it's a powerful tool. And with minimal investment you are able to create private projects as well, which has an incredible return on investment.
The sole reason we are using GitHub is because everyone else is. I would say Bitbucket and GitLab are steps ahead of GitHub, but everyone is on and using GitHub so we should as well. I'm not saying that GitHub is a bad choice, but there are other options out there that provide …
Cleaner web interface and higher uptime. Bitbucket offers free private repositories and more formal pull request review features, so it is preferred for private/internal projects, but GitHub is better for hosting open source projects.
GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
GitHub is an easy to go tool when it comes to Version Controlling, CI/CD workflows, Integration with third party softwares. It's effective for any level of CI/CD implementation you would like to. Also the the cost of product is also very competitive and affordable. As of now GitHub lacks capabilities when it comes to detailed project management in comparison to tools like Jira, but overall its value for money.
I find that google workspace covers all the bases that I would need my day to day work solution to offer. Workspace is perfect if you're someone working in sales who regularly sets up and hosts meetings. The meet solution is reliable, the transcription through Gemini is almost always perfect, and the recording function is easy to use. Calendar backs this up well by being simple and easy to use. Although having the ability to share your calendar link for people to book in meetings would elevate this further. You can also never go wrong with Gmail, it is reliable, has strong spam filters and rarely ever goes down. On the flip side, despite Docs, Slides and Sheets covering the basic functionalities that you would need to create a good base level of documents, it does lack some advanced functionalities that other providers offer. Especially in Sheets, I use sheets regularly for importing and exporting data for cold outreach, it works perfectly fine for this, but if you were looking to start creating dashboards etc using sheets as the base for this, it can start to get a bit tricky and limited.
Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.
Google Calendar...amazing. I don't need to ask team members when they're busy anymore and play this game of bouncing times back and forth. All I need to do is enter their email address and it shows my calendar and theirs side by side and then select the day and time I find that works best for the both of us.
I actually prefer Google Meet over Zoom. Zoom bogs down my computer and I find their UI overcomplicated for what it actually does. Google Meet is simple and does practically everything Zoom does without needing to pay any extra money.
Sheets integrates with our CRM (Copper) so it's perfect for us. Being able to export information out of our CRM into sheets and then create pivot tables from that data makes our lives a million times better.
Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.
Pricing is a little bit higher than other services
The cost of each email inbox costs the same whether you want just email or all of the features. For example, we wanted a support email address that we could setup our support desk with. The cost of that added account is the same as the account I use with all of the features.
They removed their free tier for small organizations like mine and restricted the free tier from adding new domain names. This was likely due to abuse, but everyone lost the privilege of the free service.
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.
There is no better solution for cloud storage and real time collaboration. The amount of features included in G Suite is unmatched and out of other things we’ve tried over the years, nothing comes close to being as great of a tool.
GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.
On the user end, it's great, probably some of the most user friendly products out there. On the admin side, it can get a little more arcane, but it's still better than a lot of other services. At worst I wrangle some CSVs to perform mass changes, but it's a far cry from the days of Powershell scripts or purely manual entry.
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
There are a ton of resources and tutorials for GitHub online. The sheer number of people who use GitHub ensures that someone has the exact answer you are looking for. The docs on GitHub itself are very thorough as well. You will often find an official doc along with the hundreds of independent tutorials that answers your question, which is unusual for most online services.
My experiences of getting support have been positive. Calling in is not overly difficult, but it does require getting a PIN. The knowledge of those responding to the calls has been impressive. I have managed to work with them to fix two Google bugs that I had identified. These bugs required a some technical expertise and the support staff were able to understand the issue and forward the concerns to the appropriate persons. The first bug was fixed with 24 hours. The second bug took a little longer, but it was also more complicated to reproduce.
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different. The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy. It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
While I don't have very much experience with these 2 solutions, they're two of the most popular alternatives to GitHub. Bitbucket is from Atlassian, which may make sense for a team that is already using other Atlassian tools like Jira, Confluence, and Trello, as their integration will likely be much tighter. Gitlab on the other hand has a reputation as a very capable GitHub replacement with some features that are not available on GitHub like firewall tools.
There are lots of competitors to various tools in Workspace, like Meet versus Zoom. However, Microsoft is the other big competitor I can think of for Google Workspace as a whole. To me, at least, the strength of Workspace is how easy it is to share and collaborate with others. For items that I only need for myself and can keep on my own computer, I typically rely on Microsoft Word, Excel, etc. For items that I need to share, I turn to Workspace a lot. Being able to collaborate in real-time and not having to send documents back and forth is so amazing, and such a time saver. And I love that Workspace is also a built-in tool with Dropbox now.
Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
Team collaboration significantly improved as everything is clearly logged and maintained.
Maintaining a good overview of items will be delivered wrt the roadmap for example.
Knowledge management and tracking. Over time a lot of tickets, issues and comments are logged. GitHub is a great asset to go back and review why x was y.