TrustRadius: an HG Insights company
GitHub Logo

GitHub Reviews and Ratings

Rating: 9.1 out of 10
Score
9.1 out of 10

Community insights

TrustRadius Insights for GitHub are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Intuitive User Interface: Many users have found GitHub's user interface intuitive and easy to navigate, making it simple for them to explore repositories without the need to clone them. They appreciate how it simplifies the process of navigating through repositories, providing a user-friendly experience.

Fast Data Processing: Several reviewers have appreciated GitHub's speed in updating, packaging, and compressing data. This fast data processing allows for quick merges and highlights code changes efficiently, enabling developers to work with agility.

Robust Version Control: Users highly value GitHub's version control functionality as it provides a historical timeline of code improvements and the ability to revert back to older versions. This feature has been praised by many for its reliability and usefulness in maintaining code integrity throughout development projects.

Reviews

131 Reviews

GitHub Review

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

GitHub is used on different levels in our organisation. From creating and maintaining a pipeline to having version control of internal products that are developed. Maintenance of data products is made easy using this because one can revert back to the old version in case there's a break in the pipeline and so on.

Pros

  • Version Control
  • Code Maintenance
  • Code Storage

Cons

  • Better Interface
  • Easier Commands
  • Larger File Upload Function

Likelihood to Recommend

Let's say you create a pipeline of ETL. You use GitHub and create the pipeline. You have tested everything on your local environment and now you're ready to push the codes. You test the codes and push them to production to be ready. Now down the line after a few iteration there comes a time when you push a change but that broke the pipeline you can simply just revert back to the old version pretty fast so that there's not a significant amount of damage with the pipeline being broken.

GitHub is the game changer for excellence

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

We use GitHub as our primary code repository for our own projects and recommended platform for our clients. We are also migrating away from our current project management and tracking tools to leverage GitHub Projects and Issues for all of our roadmap and project planning tools. We have adopted Wiki for documentation and ensured that all of our tooling is repo based for versioning and portability if GitHub ever ceases to be amazing for us.

Pros

  • Repository Management
  • Project Management
  • Issue Tracking
  • Users and Roles

Cons

  • Granular time tracking for issues/projects
  • Easier Integration into other platforms like Slack (while the connector exists - it is very basic)
  • Better notifications control around CICD

Likelihood to Recommend

GitHub does repo management really well. The granular and team based user access is very helpful and provides a robust security layer we need without a lot of thought. The project management tools are starting to be really strong with great views for planning needs. Integration into communication tools like slack or teams could be stronger

My Honest Review On GitHub

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

We use GitHub for the code repository. For all the version tracking, collaborating with multiple developer. We also use GitHub co piolet for development. Different version tracking is really helpful when it comes to the back tracking, also bug fixing. We can see where it is changed, who changed, based on the commit message we can say why it was done. Copilot gives a whole new area to play with. so much possibilities.

Pros

  • Collaboration with multiple developers. This is very good. either we can work on same branch, or we can work on different branches, then merge to the one main branch, so that all the codes are available.
  • Cherry picking is very nice, you want only one commit moved to a different branch? you don't have to merge it with complete branch, just one commit you can move.
  • Labelling is a wonderful feature, it helps to identify which branch is critical, what to touch, what shouldn't be touched.

Cons

  • Copilot plugin in visual studio seems to have some issues, it goes offline sometimes, this need to be improved.
  • Code review can be improved, merging on the page it self not that feasible, we have to resolve it offline then push it sometimes. Auto merge sometimes loses changes if complex.
  • CI/CD configuration is kind of messy, it is hard to maintain if we have to make continues changes to the file.

Likelihood to Recommend

Other that some minor improvement as I mentioned in the previous question, GitHub is a great tool which can be used to transcend your development + code maintenances good experience. It is easy to back track through the changes since the revisions are available. Also we can see what are the available branches, how many I created etc. This also helps to get a overall idea what is going on.

Vetted Review
GitHub
9 years of experience

GitHub - DevOps Platform

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

Initially we have started GitHub to manage our Code versioning and code reviews but later with time now we are using GitHub to manage our Infrastructure code as well, and it's used for all CI/CD processes in our organisation. It is integrated with other SaaS platforms like SonarCloud, Terraform Cloud, etc and for our Code Quality Check and for Infra Auto provisioning. Other than that we are also using GitHub for for project management and Issue tracking as well. We have recently started using it for our Artifact management as well. At present this tool is helping us out to manage alomost core DevOps activites at single platform.

Pros

  • Version Control
  • GitHub Actions for CI/CD workflows
  • Code Reviews
  • Third Party Integration
  • Issue Management

Cons

  • Project Management with tools can be improved further
  • Capability to Manage Infrastructure details
  • Release Managed can be improved further with dedicated tab at Organisation level with reference to pacjages

Likelihood to Recommend

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.

Vetted Review
GitHub
12 years of experience

GitHub is the ideal tool for managing version control at any organization

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

We use GitHub to manage all of the repos at our organization. We have teams of developers and also take advantage of the AI offerings available. In addition we leverage GitHub actions for deployment and wikis for documentation.

Pros

  • Intuitive interface for managing pull request and code reviews
  • Integration with AI tools make GitHub ideal for any organization
  • GitHub's enterprise level security make it a top notch solution for any Enterprise

Cons

  • GitHub could use a tool outside of enterprise level to allow merging two organizations together into a single organization
  • Would be nice to have display names that are separate from GitHub url so we can change or update repos without changing url
  • Being able to merge in 1 direction instead of a bi-directional merge would reduce headaches in some areas
  • Would love to see some built in templates for setting up new repos preconfigured with set settings and permissions

Likelihood to Recommend

GitHub is the premier service with the most cutting edge features for anyone that needs version control. It's a superior product to its competitors and easier to use. It's integration with both private and public community makes it a one stop shop solution for any developer. It's team management, security and automation integrations with AI are second to none.

GitHub is my go to

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

At Qualtrics, GitHub is a core part of our product, support and engineering workflow. It helps us support everything from day-to-day development to deployment, compliance and tracking issues and features. We use it primarily for source control and collaboration across teams, allowing developers to manage code changes, conduct peer reviews, and maintain quality. It also supports issue tracking and documentation, often working alongside tools like Jira, Notion,…to align technical work with broader product goals.

Pros

  • Integration with other products
  • Issue and bug tracking
  • Labelling

Cons

  • Community Management
  • Public upvoting and idea generation

Likelihood to Recommend

I’ve worked with Github my entire career and view it as an essential part. As a Product manager it allows me to keep track of my features, epics, issues and QA. It is easy to set up and integrate with tools such as intercom or notion.

Vetted Review
GitHub
8 years of experience

Github

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

We use GitHub for code management, collaboration, project management, and automation.

Pros

  • Pull request and code review.
  • Github actions for CI/CD.
  • Branch protection.

Cons

  • Complex permission management for large organizations.
  • Limited advanced search.
  • Github actions limitations for complex workflows.

Likelihood to Recommend

It is well-suited for collaborative development of Dockerized web apps. Very useful for managing open source contributions. Not much suited for managing large-scale enterprise permissions.

GItHub for secure and scalable software development

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

At our organization, GitHub is used as a central platform for source code management, version control and collaboration across Dev and QA teams.

Pros

  • Pull request workflow and code review
  • Integration with CI/CD
  • Issue tracking

Cons

  • Limited built in test reporting in GitHub actions
  • Project management features are basic

Likelihood to Recommend

1) It is very well suited for CI/CD for automation testing. GitHub actions enable seamless integration. 2) Version control for agile development. Features like branching, pull request and protected main branch are crucial.

Great for team collaboration

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

we use it to maintain our source code, use it for cross team and inter team collaboration. Single source of truth and deployments.

Pros

  • code reviews are great
  • deployments and ease of use are great
  • maintaining docs is good too

Cons

  • sometimes the code review button bugs out, it’s weird to have both comment and review in one popover
  • GitHub lottery tool that can be configured on GitHub UI for reviewers would be good
  • being able to add reviewers automatically when they’ve added any comments would also be good, so everyone can see before they click in

Likelihood to Recommend

it has also been a really good tool for collaboration, and in 99% of cases it’s very intuitive

Vetted Review
GitHub
10 years of experience

Not the best solution for any org larger than 10 people. In my opinion, support does not exist

Rating: 1 out of 10

Use Cases and Deployment Scope

We use GitHub for our code repository, CI/CD and Issue tracking. We have about 50 devs on the system who uses the platform including myself.

Pros

  • Code Repository
  • Issue Tracking in PRs

Cons

  • In my opinion, support is horrible - well it doesn't exist so
  • Issue tracking needs some revamp for searching and text editor
  • In my opinion, they must stop acting like God and delete users and their history!

Likelihood to Recommend

Several major problems that are forcing us to look at alternatives and move away but the most critical one is that they deleted a user of our account and all the issues that the user created! In my experience, all gone with no explanation. You disable/delete a user, okay fine, but why in the world delete the issues they created that need to be tracked and fixed?

Then, where the heck is your support team? In my experience, it's been over a week and created a ticket but they haven't even acknowledged it. I have replied 4 times to that ticket but they have failed to even say, got it, let us figure out where, in my opinion, GitHub screwed up!