GitHub Reviews

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
440 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 9.2 out of 101

Do you work for this company?

TrustRadius Top Rated for 2019

Overall Rating

Reviewer's Company Size

Last Updated

By Topic

Industry

Department

Experience

Job Type

Role

Reviews (1-25 of 107)

Tim Hardy profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
We are using GitHub in our development team as our source control solution. GitHub allows us to easily work from either the office or remotely. Git's distributed version control makes branching incredibly easy, and GitHub provides the most seamless and easy to use Git solution I have found. GitHub provides a ton of integration options with any tool you are using.
  • GitHub makes it easy to research and find what code changed and when.
  • GitHub is easy to integrate with other tools.
  • GitHub is reliable and dependable. I've used it for nine years without issue.
  • When browsing history of a file, GitHub could make it easier to see the file after a particular commit instead of just being able to quickly view the commit. I'd like to be able to see the commit or the file itself in one click.
  • I would like to be able to view commits by user.
  • I would love to be able to traverse code on GitHub (go to definition, etc) - the good news here is that they are working on these features!
Any scenario where source control is needed is a scenario where GitHub is well suited - that means, any time you are writing code and don't want to immediately throw it away once you are finished. GitHub is especially well-suited for remote work and any work where integration with third-party tools would prove helpful.
Read Tim Hardy's full review
David Crawford profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
The development department uses private GitHub organizations for version control of web applications and internal analytics programs. Only development uses it, the other departments do not create new code or interact with it so it's only been appropriate for us.
  • Code difference comparison
  • Private repositories that are stored outside the organization
  • Code highlighting for ObjectScript
  • Issues tracking is easy to attach to commit history
  • Syntax highlighting for more obscure file types, like csp (Cache Server Page)
  • Better handling or notification of deleted forked repos. If you delete the repo, the pull request will show up as "unknown repository" which creates odd dead ends
Well suited for version control of any type of code, especially in a sensitive environment. You can also set up your own private server if you don't want it stored on their servers. GitHub will provide details of storage and transmission methods so that you can verify if everything is HIPAA compliant.
Read David Crawford's full review
Frank Ramirez profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
GitHub is our primary code repository for the company's web app. It allows us to effectively collaborate as a team on our codebase, while providing an easy system to track and manage changes. GitHub essentially serves as the Google Docs for our code. Specifically, it allows multiple software engineers to work on the same code in a separate environment that protects the primary codebase and is only merged in when it's working as expected. This allows for all kinds of collaboration, including with remote workers all over the world.
  • GitHub's ease of use is one of its biggest strengths. The site is structured around Git, a code version control system, which is used by developers around the world. GitHub's UI is minimal and allows you to focus on what's important, whether it be your branches, pull requests, or issues.
  • GitHub's integrations and tools are fairly ubiquitous. You'll likely find an integration with GitHub on every development tool with integrations. This makes it easy to incorporate in whatever workflow you may have.
  • GitHub is incredibly reliable. I don't remember the last time it was down for any significant period of time. This is essential for companies that rely on it for their daily operations.
  • While GitHub's spartan UI gets the job done and doesn't distract, it has some room for improvement to make things even more intuitive, especially for newer users. There's a certain amount of learning curve that could be made less steep.
  • There's so much you can do with Github that it's fairly common for a user to possibly only use a small fraction of what GitHub can do. Improving Github's discovery features would help surface some of the non-essential features that are quite useful.
GitHub is uniquely suited in situations where distributed teams need to collaborate on the same codebase. It allows non-destructive work in the form of branches that allow you to merge working code when it's ready. Different software teams can work on different parts of the codebase and each have an approver that serves as the gatekeeper for the merged code. This protects the primary codebase from non-approved or buggy code.

There aren't many situations where you should use GitHub. Even a single programmer would benefit from using it. Furthermore, it has other uses related to issue tracking and documentation that increase its value.
Read Frank Ramirez's full review
Richard Davies profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
GitHub is used by some development teams across our large organization, including our small web team. It's used as a central code repository for storing our website code and allows multiple developers to work on separate branches simultaneously, then merge those changes into the main branch once their work is finished. It also keeps a history of changes so we can tell who changed things and when they were changed.
  • Seamless integration with Git. Although you can use Git without using GitHub, the two have become almost synonymous.
  • It provides a nice web-based UI for interacting with your central Git repository.
  • Facilitates working with multiple branches, forks, and pull requests—all different aspects of having multiple people working on the same code simultaneously.
  • Honestly, I'm having a hard time coming up with any cons or things I would change.
If you use Git and have multiple people working on the same code, then GitHub is for you. If you're a sole developer and don't need to share or publish your code, then you might not have much need for GitHub.
Read Richard Davies's full review
Emeka Opara profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
GitHub is being used by the information technology department to work concurrently on projects we are looking to implement in the coming months. It addressed the issue of having to work together and input code from various locations.
  • The ability to access GitHub on multiple platform makes organizing files very easy.
  • GitHub is intuitive enough to help new users immediately understand its platform and how to use it. It has instructions and help notes at every turn to help with this and the UI is user-friendly.
  • The best aspect of GitHub in my opinion is its ability to track your activity and also shows you a working map of of your activity over time. This can help with planning and scheduling of one's work.
  • I think GitHub should incorporate two-factor authentication to improve user account security.
  • The Macbook GitHub application could be improved to be more intuitive.
I think GitHub is well suited for individual or group projects. However, I cannot think of a scenario where it is less appropriate but not customizable to fit the situation. GitHub is highly customizable to fit various situations and uses.
Read Emeka Opara's full review
Ray Flores profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
Github is being used for version control and feature branches for our main website. The tech team is the only person with access to push or pull from the repository. Our industry is changing very rapidly, and so, the tech team is charged with adjusting our front-facing website hourly, and sometimes this causes conflicts when one of the team members is also doing a similar task. Thus, GitHub allows us all to stay in tune and be in perfect unison when it comes to deploying code out to the web.
  • Version Control - You can see the progression of where you started to where you are today, and if need be, rewind to a certain time in the past and use that version if need be.
  • Storage Space - There are really no limits to the amount of information you can keep in one place.
  • Collaboration - Contributors can be one or can be many, and GitHub keeps track of each instance by the author.
  • UI - Although there is a readme file that can be made to look pretty, over the UI is very dry.
  • App or web app - If there we an easier way to integrate with GitHub versus the command line, I am sure the number of users would increase dramatically.
  • Glossary of Actions - There is not one place to which one author could go to find an absolute glossary of what actions do and what those actions are. Very hard to decipher the amount of information available on the web.
For software developers, web developers, and code developers in general, GitHub allows you to actually see your developments historically, and there is no limit amount of stored history that I am aware of. Keeping your code to look back or even reference from time to time is a great well worth the cost associated with both mental and physical costs.
Read Ray Flores's full review
Bryan McAnulty profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
Our design and development team uses GitHub. About 10 years ago we used to use SVN instead of Git and we tried some cloud services for hosted SVN repositories. At the time we felt that Git was more focused specifically on open source software projects, didn't have GUI clients for designers, and didn't have the project management-oriented features that we wanted. That has completely changed since then, and now Git and GitHub specifically is the perfect solution for our team. GitHub helps us build great software, and integrates with many services we use to help us be more effective with a distributed team.
  • Integrations with services like Heroku that allow us to deploy staging environments from a pull request.
  • Familiarity with other developers making it easy to add a collaborator to a project and have them make a productive impact on the project right away without learning new tools.
  • It makes it easy to review and collaborate on open source projects and private ones.
  • It has many GUI client options for those who are not as comfortable with the command line.
  • Helpful reporting of contributor activity and built-in project management features like docs and comments.
  • In some ways, the design of GitHub incentivizes the use of certain practices like using pull requests, which may not fit your organization's workflow (though I don't really see this to be an issue personally, and if your organization isn't using something like pull requests, then I would question why).
GitHub is the best solution for code version control and collaborating on software products. If you are specifically a writer for instance and want to collaborate on a piece of copy with someone else, GitHub can work for that too, but it isn't really suited for version control outside of software.
Read Bryan McAnulty's full review
Brett Knighton profile photo
October 12, 2019

GitHub Review

Score 6 out of 10
Vetted Review
Verified User
Review Source
GitHub currently isn't the main product we use for hosting our repositories. We primarily use Bitbucket currently and have plans to move to Azure DevOps whose repository hosting/management is re-skinned GitHub. My use of GitHub has primarily been working with open source libraries.
  • I prefer the way GitHub presents/manages code reviews.
  • Making changes and opening pull requests are incredibly easy in GitHub. When you have a small change you need to make it's incredibly annoying to have to pull then branch then commit then push then go back to the browser to open a PR.
  • Built-in wiki, issue tracking and reporting, and other tools can be incredibly useful.
  • Browsing through a repo is pretty primitive. Digging into a folder is a link to a new page. For medium to large repositories, it's extremely cumbersome. The way Azure DevOps manages this is incredible. It gives you a folder explorer as you'd find in VS Code. You can quickly browse through a complex repo and make in line changes and submit a pull request all from inside the browser.
  • Navigating around a GitHub repo can be a little confusing until you're used to it.
For small team projects or open-source libraries GitHub is a great and affordable option. I'd be more hesitant to use it with large complex projects, not because it wouldn't work, but because I've used tools that are better suited. I'm sure Microsoft won't be mad at me for continuing to put in plugs for Azure DevOps seeing as they own both.
Read Brett Knighton's full review
Mark Nowowiejski profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
Git Hub is not used in any official capacity but there are numerous staff (developers), instructors and staff that use this industry-standard platform for sharing code and working collaboratively on websites and apps.
  • Great for sharing code and collaborating with the coders around the world.
  • Versioning: By installing Git on your local machine and taking a regular snapshot (called commits) you can restore your project to any previous point without having to keep multiple versions of your files.
  • I consider GitHub to be social media for coders/developers if social media was actually useful. There are tons of free resources and the community is fantastic.
  • With GitHub you can host a simple static website for FREE (which is better than AWS s3 buckets IMO)— this is a great alternative to vendors like GoDaddy or BlueHost, etc.
  • The UI isn't super intuitive at first but help is easy to find.
If you are out applying for web design/developer jobs and don't have a GitHub account it will very likely work against you. Having a solid understanding of version control, branching and managing your files with GIT through the terminal via command line is no longer an optional skill
Read Mark Nowowiejski's full review
Valeri Karpov profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
All our source code is hosted in private GitHub repos. All code reviews also go through GitHub and our deployment process goes through GitHub as well, pushing to the master branch triggers a GitHub webhook that deploys the code to production.
  • Excellent integration with CI/CD tools: testing and deployment are easy via GitHub's ecosystem.
  • Great code review tools.
  • Easy to link to and share specific lines of code to communicate with engineers.
  • Notifications are noisy by default and hard to configure to do what you want.
  • No cross-repo issue tracking, hard to see all open pull requests at once.
  • We pay per seat, which means sometimes we introduce extra friction because we can't give everyone access to our GitHub.
GitHub is my de facto choice for hosting code. It comes with excellent code review tools, issue tracking, project management, and security issue tracking out of the box, and makes adding testing and deployment easy. GitHub is also one of the best project management tools out there. At previous companies, we would create empty GitHub repos just to let other teams use GitHub issues for tracking goals.
Read Valeri Karpov's full review
Eric Mason profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use Github extensively for version control and team collaboration in all of our development/architecture projects. It's primarily used by our product team but we also use it to share information with the success team and collect feedback. Github assists us in the process of code reviews and is a powerful tool when managing/deploying multiple simultaneous projects.
  • Version Control: GitHub, being built over Git, makes it fast and easy to develop projects in versions/branches and easily rollback to previous versions when necessary.
  • Pull Requests/Review: GitHub has a powerful UI for creating pull requests, with useful tools like inline commenting and more recently "suggested changes". Pull request history is always maintained and easy to search.
  • Collaboration/Auditing: It's easy for multiple team members to work on the same project and merge changes (often) seamlessly. All contributions are tracked so it's easy to identify contributors.
  • Industry Standard: GitHub is used by virtually all major open source projects so it's very easy to find and contribute to projects of interest if you're well versed with GitHub.
  • Reviewing large pull requests can be tedious and it can be tough to identify recent changes (e.g. a one line change) in new files or files with lots of changes.
  • It should be a bit harder to push unresolved merge conflicts, we've had these slip through once in awhile.
  • You have to be careful with merge operations; a bad merge can be painful to reverse.
Situations where Github is well suited:
- Pretty much any development project (solo or as a team, it's always useful to have backups/project history; you never need to worry about losing your work if you commit/push regularly)
- Projects involving multiple collaborators with and a structured text-based syntax

Situation where Github is less appropriate:
- It's less useful for situations where you have multiple collaborators working on written/formatted reports; I've found Git can produce some nasty merge conflicts in these situations
Read Eric Mason's full review
Kyle Taylor profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
We currently utilize GitHub as the default code repository host for clients who either don't have a current version control system or for internal projects that need hosting. It's primarily used across our whole delivery team, while projects from other departments may be hosted there as well.
  • Github integrates really well with 3rd party systems, especially those used for continuous integration.
  • Github provides a number of built-in tools to support the project management process.
  • Github is ubiquitous in the sense that it's rare to find a platform or organization that hasn't used it, making it much easier for onboarding.
  • Some of the extended features, like "Projects", can be a little too lightweight and users may spend too much time setting it up and not end up using it.
  • The process for accepting invitations is kind of odd and doesn't always provide direct instructions to end-users.
I believe because GitHub has become so ubiquitous, there aren't many technical or code-based projects it isn't suited for. Even for repositories that are strictly for documentation, it serves well as for revision controlled documents. There can be some limitations through the integration APIs that other platforms like Gitlab may be able to fill better.
Read Kyle Taylor's full review
Benjamin Plotkin profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
Our department uses GitHub as its dedicated private repository for our production-facing web applications. In general, GitHub is popular across our organization (a public university), especially for students. GitHub gives us a high-quality, secure, cloud-based Git repository system at no cost, allowing our team to safely store application code, and to pull updates to our test and production environments, with minimal effort.
  • GitHub is a great, free or low-cost cloud-based Git repository system for smaller teams; it's easy to add members and collaborators to one or more repositories, as well as to modify user roles and rights.
  • GitHub provides a handy and highly transparent front end on top of the renowned Git system. Visibility into developer productivity, including code commits, is well-represented in GitHub's dashboards.
  • GitHub provides extremely detailed and focused user support documentation online, allowing every team member to build their Git skills incrementally while ensuring that most basic issues are handled quickly via end-user self-service.
  • GitHub packs a lot of functionality into its website; sometimes it can be difficult to navigate to the correct sub-page; the various drop-down selection boxes and sidebar menus can be confusing to users, especially ones with lightweight experience with the interface.
  • GitHub allows for substantial flexibility in user account management - Administering dedicated team members and collaborators across a large number of repositories can get tricky, especially if users have varying access rights or roles across various repositories.
  • Knowing the difference between user and organization accounts is key, there have been many times where I've wasted minutes looking at the wrong account trying to find a relevant setting or feature. For example, to view correct account billing information, one must be on the organization account, not the user account that has administrator rights for the organization.
GitHub is a great, free option for individuals, who can take advantage of unlimited public and private repositories. For team-based organizations, it's a reasonably low-priced, high-quality way to reap the benefits of a cloud-based repository system. Larger organizations with multiple teams may find hosting their own Git servers to be a more cost-effective option when compared to GitHub's Enterprise pricing plan, but said plan's support for cloud and self-hosting options allows enterprise users to have their cake (on-premises ownership of code repositories) and eat it, too (use of GitHub's sophisticated web-based front-end to Git).
Read Benjamin Plotkin's full review
James Hilton profile photo
October 09, 2019

Works Perfectly

Score 10 out of 10
Vetted Review
Verified User
Review Source
GitHub provides us with access to open source software and small scripts of code that we can use instead of writing the code ourselves. Knowing that the code is critiqued and improved by other developers and generally follows best practices, this allows us to analyze it's suitability and compatibility quickly. GitHub provides logs of the changes to this software to assist in bug finding and allows us to contribute to the software if we require a change.
  • GUI for source control is great.
  • Storing source code efficiently with simple commands.
  • Searching for code is in a code base is easy and works well.
  • Atom takes too long to load.
GitHub is great for storing code, finding other people's code, analyzing good coding practices, and stumbling across really bad coding practices.
Read James Hilton's full review
Csaba Toth profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
GitHub is primarily for managing software source control, issue tracking, developer collaboration, CI/CD. We use it for source control, peer review, and server-side merge, CI/CD capabilities like automated test suite running for PRs and merges. We use a separate issue tracking system, but for many projects GitHub's built-in issue system is adequate, it has advantages like automatic issue references and linking of issues to commits, PRs. GitHub also offers wiki pages per project, team organization, and one of my favorites is its free static website hosting service called (GH-pages). Their static hosting is capable of consuming Jekyll (Ruby on Rails) based projects on the server-side. Open-source repositories and organizations are free of charge with a 1GB limit per repo. A limited number of private repositories for individuals (not organizations) are also free. GitHub can perform security checks of the packages used by the project and even propose recommended fixes to those in the form of generated PRs. Speaking of automated PRs GitHub offers extremely easy few click solutions to contribute bugfix PRs to open source projects and other actions can be performed solely using the web front-end.
  • Free hosting of open source projects and a limited number of private repositories as well for individuals.
  • Free website hosting of statically generated websites or Jekyll Ruby on Rails-based projects.
  • Issue tracking, pull request system.
  • CI/CD capabilities.
  • Enforcing rules like PR needs to be accepted for a merge and other team management and policy features.
  • Widely adopted, large user base.
  • Very friendly and easy to use UI, many tasks can be done through the web.
  • Organizations without a paid plan cannot have private repositories.
  • Free repositories have a size limit of 1GB.
  • Support could be slow to respond.
  • Migrating repositories to other services can be hard.
Although support could be slow to respond that's not always the case. I'd also not decrease my rating because they don't offer free private repositories for organizations. They need to generate some profit from somewhere, and their site is very reliable and easy to use. I'm also not concerned that GitHub was acquired by Microsoft. There are extremely viable alternatives though.
Read Csaba Toth's full review
Sanyam Jain profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
GitHub is the most used tool in my team. I have been using this for a long time. I am really excited about committing updates to open source community and getting green commit dots on my profile as these green dots reflect your active time on GitHub. Every new update in our program, we commit to GitHub.
  • Multi-platform support, Linux, Windows and Mac.
  • Growth to Open Source Community.
  • Recruiters can check the GitHub profile than reading the complete CV. Even I prefer to share my GitHub ID than complete resume. As GitHub is your new CV.
  • Best way to showcase your talent to open source development.
  • GitHub requires attention over an android app. There are numerous third-party applications but not an official application.
  • GitHub requires more improvement to make it industry ready app.
  • One cannot use only github in their company for real time and live databses and applications.
Well suited for:
- Small level projects are well to design and easy to manage
- Faster integration with 3rd party applications
- Job applications and outsourcing skill sets
- Showcasing your development
- Now support private repositories too.
Read Sanyam Jain's full review
Tim Noetzel profile photo
October 18, 2019

GitHub Delivers

Score 10 out of 10
Vetted Review
Verified User
Review Source
At our company, all Engineering and Product Design team members use GitHub. We use its code repository, version control, and ticket tracking tools to store, maintain, and manage code for various projects. It works incredibly well at all 3 functions and is an extremely vital tool for our entire organization.
  • Version Control
  • Code Repository
  • Ticket Tracking
  • UI for non-technical users
GitHub is a fantastic tool for software orgs that need to securely store their code, manage versions, and track bugs, enhancements, and the like. It's not especially suited for non-technical users.
Read Tim Noetzel's full review
Jacob Biguvu profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
After cloud migration, GitHub becomes obvious for use, especially its automation. The whole organization is using the GitHub as a hub. It works like a Repository where Developers, DBA, and QA keep their artifacts; and make them visible or accessible to the team. It works as a shareable location for the team. It works as the shareable location for all automate jobs. GitHub is a great Hub.
  • GitHub is a place where we can keep the artifacts such as source code, lookup data, and other callable information. GitHub can be integrated with deployment tools such as Jenkins, TeamCity and any cloud DevOps tools. These tools can call/read the code or data from GitHub which works as a hub or repository.
  • GitHub works as version control. Meaning, when you upload the code script with multiple changes, the GitHub stores old copies as versions. If you want to restore back to the point-in-time code script, GitHub provides you to restore it. So GitHub gives security over your code.
  • GitHub provides public and private access. Public is free. Private charges. For proof of concept projects, development or testing, we can use PUBLIC access which is cheap or free.
  • GitHub is great tool. when you want to push a code change or small update, you would need to required to pull the entire GitHub repository unto your PC. This need to mitigate.
GitHub is the best at keeping the artifacts which are called through automated scripts.
Read Jacob Biguvu's full review
Ashish Balure profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
In our org, GitHub is not just used by developers but also by PMO teams to version control the documents which has a fabulous controlling which helps in maintaining the content of the files.

As per its flagship functionality of forking which is duplicating a vault starting with one client's record then onto the next - this empowers us to take an undertaking where we don't have compose access and change it under our own record. In the event that we make changes we'd like to share, we can send a warning called a "pull demand" to the first proprietor.
  • Fork
  • Pull Request
  • Merge
  • Only for premium users to use
  • File size limitations
  • Private repositories for free accounts
Git enables clients to share codes, content sections, or any data with different engineers. It very well may be utilized for content trade, Ggits functions andGit vaults. In this way you can simply bifurcate them and update their forms. So on the off chance you use it in an open source code site, it can very well be a genuine option. Defect tracking in GitHub coordinates this component to disentangle search and bug fixing. To comprehend what ought to be done, a designer just opens the dashboard of each venture and channels the data. Questions can likewise be arranged by their ubiquity, update time, etc.
Read Ashish Balure's full review
Dillon Welch profile photo
July 18, 2019

Great software!

Score 10 out of 10
Vetted Review
Verified User
Review Source
We use GitHub to host our code, back it up with source control, and as part of our software development life cycle via code reviews using the pull request feature. We also use GitHub to review the code of open source libraries and contribute to open source in general.
  • Source control
  • Reviewing code
  • General ease of use
  • Searching through code
  • Outside collaborator functionality makes it hard to assign permissions correctly.
GitHub is great for any organization who uses Git and needs to store its code somewhere accessible to all their developers. It's also great for an organization with open source projects. It's not appropriate for an organization who wants to retain complete control over their code.
Read Dillon Welch's full review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source
In my organization, GitHub is used by the development team, so everyone can keep track of the version control for the code we produce on a daily basis in projects.
  • It's easy to use and has a very intuitive platform on the web.
  • There's a whole bunch of tutorials online about how to use GitHub via the command line.
  • Anyone who codes can create a free account on GitHub and start contributing with code.
  • We can only have one private repository with a free account.
GitHub is appropriate when you work on small to medium size projects, but for something bigger, you should consider Bitbucket.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source
It's used for managing source code primarily, and we use it to collaborate as a team across our various software projects. On a daily basis, our organization will use it for git source control. It's also used sporadically as a wiki, along with as an issue manager when needed. Though for most issue management, JIRA is used instead.
  • Git sources control.
  • Issue management.
  • Wiki for a project.
  • Release management.
  • Finding open-source code.
  • Not open-source itself.
  • It only offers Git control.
  • Poor search feature at times for popular languages.
When it comes to source control, GitHub is an exceptional service and you can't go wrong selecting it for a project. As a personal preference, I prefer Gitlab, but GitHub is great. If you need to manage the source and want to keep a basic issue tracker along with the project, it's very well suited.
Read this authenticated review
No photo available
Score 9 out of 10
Vetted Review
Verified User
Review Source
I use GitHub for personal projects to host my codebase for JavaScript-based web applications and projects used for learning different frameworks. It's one of the few major players between (others being Bitbucket and Gitlab). We don't use it at my day job because they only recently offered private repositories. We don't have open-source projects at my current company.
  • It's very easy to use. It walks you through much of anything that you may have questions with. Like how to link a local repo to your online one.
  • It's ubiquitous. So many open-source projects are hosted on GitHub.
  • Integrations abound: With that ubiquity, you get some great benefits of tie-ins existing and new tooling. For example, there are continuous integrations for deployment and cutting-edge integrations with tools like Zeit Now and Netlify.
  • They have some nice-to-have features like security bots that will auto bump versions of dependencies for your project (if you desire.)
  • The social aspect of it is pretty nice and works well.
  • It's a good thing to have for a developer resume.
  • Git can be cumbersome and confusing as a whole, so sometimes the UI is a little too basic.
  • It got bought by Microsoft.
Now that it has private repositories, I feel like it is much easier to recommend. It competes better with Bitbucket and Gitlab as a result. If you don't mind it being bought by Microsoft, you get a more integrated widespread tool. New technologies like Netlify and Zeit's Now services were early to adopt GitHub repos as a source to pull code repo images from before they integrated with Gitlab and Bitbucket. So going with GitHub does get you in the door with other tooling faster. As the new guys (like Gitlab) gain more and more traction, these benefits probably go away and it's up to more personal preference and the UI.

But then again, having a "GitHub profile" is a worthwhile endeavor for any developer looking to get a job.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source
GitHub is the Version Control system used across the company by all the departments. It is hosted well within the company data center and every employee has a user created in the centralised GitHub. There are many organizations created for different projects/departments as per the need. Users can have both public and private repos in their own user profile. Though the user makes a public repo, it is still accessible only to people within the company as it is hosted inside datacenter and not accessible to open public. It is the recommended SCM across the whole company.
  • Branches are links and trees instead of a replica.
  • GitHub gists are very good and helpful for storing and referring commands and scripts.
  • Github pages lets user/organizations have static websites without a need for hosting services.
  • The transparency and fine grain access control for Pull Requests, including constraints on reviews and mergers are too very good.
  • The wide range of GitHub APIs help Automation engineers to automate lot of work flows, especially WebHooks.
  • Pricing. There are other tools like GitLab which have similar features and are free.
  • File size restrictions. File size cannot be greater than 100 MB.
  • The Project Management section of github is not very great.
From the developers view, it is a very good tool to track issues and write code accordingly. The lightweight branches help in the workflow a lot. Developers of a project can decide on one of the branching strategies and work well in collaborating without the worry of code and file integrity. Can have peer reviews with the fellow collaborators for better quality of code. It is well suited for projects with collaborators as less as 1 to quite big teams of 100s of collaborators.

From the Automation team perspective, Github has many APIs and third party integrations which help in automating the workflows like CICD. Teams can write apps on top of GitHub APIs to do more analytics on the developer productivity and much more.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use Github Enterprise across our entire IT organization for hosting our project repositories. It solves the problem of source control for enterprise applications and it does that really well. It also has solid API's and its very well integrated with other Continuous Integration tools, that makes its customization quite easy.
  • Easy and intuitive UI. This is a big plus for anyone wanting to just explore the repository without cloning it.
  • Solid security model for repositories. You can provide Dev access or limited access to the repositories that enable collaboration across the org.
  • Robust Pull Requests (PR) model. We use PR to do code reviews and the PR feature set is easy and intuitive. You can request PR's for other dev's, they can write comments at a specific line of code and you can reply back to that comment using their UI. All of this enables healthy communication on code.
  • Endless customizations. Github is wildly popular, so it has solid integrations with other developer tools. You can also add webhooks to trigger deployments when a new branch has been merged into Master. This allows for a seamless continuous integration pipeline.
  • Robust API documentation. The older version of Github offers easy REST interface and their newer API implementation uses GraphQL, which is robust and allows Dev's to build their own tools on top of Github
  • Branch Protections. You can protect a specific branch on your repo and restrict who can directly commit/delete that branch. This prevents unintended code base deletions .
  • Project tracking using Github. Github also provides tracking using its interface. You can create development tasks, assign them and track the left over work using the Github interface. Which makes it a one stop shop for everything.
  • The Pull Request screen would hide the previous comments when a new commit has been made. This could be a bit confusing tracking all the comments on a PR.
  • The network tracking branch could also use some improvement. It's hard to track all the open branches and where they all merge on the repo. The screen could use some improvement.
  • It does not provide integrated CI tool. There are competitors of Github that provide integrated deployment tool and Github could use that improvement.
It's well suited if you want a no-nonsense version control for your organization. GitHub is quite popular and you have tons of solid integrations that would simplify your continuous integration pipeline. The open source git tracking allows you to work while you are offline, so you don't even need to be online all the time to make the commits. However, GitHub is a bit expensive compared to Gitlab or other alternatives. So, if cost is a concern, I would look elsewhere.
Read this authenticated review

About GitHub

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. 
Categories:  Version Control

GitHub Technical Details

Operating Systems: Unspecified
Mobile Application:No