Git Reviews & Insights

Score10 out of 10

73 Reviews and Ratings

Community insights

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

Business Problems Solved

Git is a widely used version control system that offers a range of use cases for different teams and organizations. Engineering and dev-ops teams rely on Git to handle version control of codebases, allowing them to create branches for features and bug fixes. By using Git, they can easily merge and release code to different environments, ensuring smooth software development processes.

Freelance software developers also find value in Git as it enables them to work on multiple machines and platforms, providing flexibility and backup of source code. They appreciate the ability to easily manage and track changes in their codebase, ensuring effective collaboration with clients and the ability to revert back if needed.

Organizations benefit from Git's ability to store source code across multiple repositories and branches. They typically have a mainline development branch for code review and automated builds, allowing for efficient management of projects. Git addresses the problem of multiple people updating a codebase by managing merging of changes, storing committed changes in a log for review, and offering rollback options when necessary.

Furthermore, Git fosters collaboration and code contribution among developers by preventing conflicts and facilitating efficient software development. It is successfully utilized by various departments like Tech Writing and Implementation, helping streamline release cycles and integrating smoothly with other tools like Bitbucket for pull requests.

Additionally, Git is an essential tool for managing app development processes. Its usage ensures faster release of changes while minimizing negative impacts on existing functionalities. Many companies rely on Git to manage massive codebases and enable cross-team code review, making it a reliable solution for tracking project progress and ensuring software security vulnerabilities are addressed.

Overall, Git's ease of use and cleaner approach to version control have received praise from users. It is widely recognized as stable and reliable for managing code, providing a centralized area for sharing and collaborating on projects across different teams.

In summary, whether it's handling version control, managing projects for customers, tracking changes in websites or internal scripting projects, or enabling concurrent work, Git proves to be a valuable and versatile tool for developers, freelancers, and organizations alike.

Git Reviews

12 Reviews

Enterprises (1,001+ employees)

The cornerstone of collaborative development

Rating: 10 out of 10

Incentivized

January 5, 2024

Use Cases and Deployment Scope

Git is a software version control system that enables distributed collaboration of engineers working all over the world. It allows for development on parallel features, acting as the source of truth for code, and also detects and helps solve conflicts that might arise from collaboration on the same files.
I'd say Git is one of those systems that are pretty much omnipresent when it comes to the Tech industry at this point. I haven't come across a simpler, better distributed version system yet.

Pros

Version Control
Conflict Resolution
Collaborative Work

Cons

UI
Learning Curve

Likelihood to Recommend

Git is suited not only for software work, or the tech industry as a whole. It's true it's the most obvious use but I've recommended Git for people in various industries, from finance to art. The truth is that if you're working on files that are meant to be worked on by other people as well, in a collaborative effort, I would without a doubt recommend Git.

Gabriel Freire

Senior Staff Engineer in Information Technology at Equinix (Computer Software, 10,001+ employees)

Vetted Review

9 years of experience

View profile

Git has everything you need for code

Rating: 9 out of 10

Incentivized

June 28, 2021

Use Cases and Deployment Scope

Git is used across the organization for version control of the code build. It helps us track our deployments and snapshots of various artifacts we develop. All kinds of programming languages and files are checked in to git via github. We also control the code migration between various environments using Git.

Pros

Pull requests to control what's checked in where
2-step commit and push to enable cleaner check-in process
Personal forks to help developers with quick development and testing

Cons

I feel that code merging using command line is not very straightforward when there are conflicts

Likelihood to Recommend

Git is well suited for code that can be versioned. It cannot be effectively used for auto-generated code files from tools. For instance, Git is well suited for any code that we build using languages such as Java, python, scala, node, etc. However, the java code generated from tools such as Talend are not very well tracked when we use Git.

Verified User

Employee in Corporate (Information Technology & Services company, 10,001+ employees)

Vetted Review

4 years of experience

Git is the VCS King

Rating: 10 out of 10

Incentivized

January 23, 2020

Use Cases and Deployment Scope

Git is being used as version control software to merge different sets of code together and keep a log we can look back on if problems occur. I don't think there is any real competitor to Git. It can also be used to try to track your commit level vs others.

Pros

Better merges than anything else.
Logging.

Cons

Still some confusing merge issues.
I would like to see a system IDEs can use that automatically notifies you if someone pushes.

Likelihood to Recommend

In my opinion Git is always best suited for every version control and anything but the most simplistic of temporary code should be version controlled. It takes so little effort and can save your entire application. SVN was much worse at merging when I used that for a couple years.

Josh Stapp

Sr. Drupal Developer in Engineering at ICF Next (Computer Software, 1001-5000 employees)

Vetted Review

6 years of experience

Verified on LinkedIn

Every developer should be using Git

Rating: 10 out of 10

Incentivized

January 18, 2020

Use Cases and Deployment Scope

We use Git as source control for all our projects across our entire department. I know there are other departments in our organization that use it as well. I also use Git for all my personal projects and side projects. Git enables all of our developers to collaborate and contribute code to our projects simultaneously, preventing conflicts.

Pros

Source control
Collaboration

Cons

Difficult for people who aren't used to the command line (but there are apps for that).
Some specific situations where it's difficult to figure out the right way to do things.

Likelihood to Recommend

Git is great for pretty much any coding project, whether working on a team or with a single developer. For teams, it enables multiple developers to contribute without getting in each other's way. Git also keeps a history of all code changes, which is why I would also recommend using it on projects with a single developer. The only real scenario where I would maybe not use it is when working with non-tech people. But even then, I might recommend getting them set up with a Git client app and teaching them how to use it.

Nate Dillon

Front-End Web Developer, Office of Mediated Education in Information Technology at Kansas State University (Higher Education, 5001-10,000 employees)

Vetted Review

8 years of experience

View profile

Easy to use and collaborate

Rating: 6 out of 10

Incentivized

January 18, 2020

Use Cases and Deployment Scope

Git is used mostly as a source version controlling system which allows developers to collaborate with one another. It helps teams to contribute to various projects by pushing code to GIT. It can be used for release versioning. It is helpful to know which version has been released in production and at what codebase.

Pros

Flexibility
Version history

Cons

Merge conflict
Amending commits in remote repo

Likelihood to Recommend

Git is well suited for collaboration. It can be used for multi-branch repositories and managing branch-heavy workflows. Collaborating is easier in Git. The disadvantage of using Git is that it is less secure. If the project is open source then it is fine, but Git charges for having a secured repository. Meanwhile, it offers private repos for free tier licenses.

Verified User

Engineer in Information Technology (Banking company, 5001-10,000 employees)

Vetted Review

5 years of experience

Git: Branches are cheap, damn cheap

Rating: 10 out of 10

Incentivized

December 19, 2019

Use Cases and Deployment Scope

It's widely used by our component owners to store all the libraries. The beauty about Git compared to others is that it stores snapshots instead of deltas, which makes it just much much faster and more reliable to store code within it. We have integrated Git with Gerrit which stores the whole organization's Git repos within it, thus making it more reliable and scalable.

Pros

Fast.
Robust.

Cons

This tool is just perfect.

Likelihood to Recommend

It is well suited for scenarios wherein you need to manage a lot of code and multiple developers are working on the same repository. The whole point of using Git is that you can create branches, develop the code on it, push it up and again keep on doing this. If you are not creating 10 branches a day you are not using GIT well.

Verified User

Engineer in Engineering (Computer Hardware company, 10,001+ employees)

Vetted Review

3 years of experience

GIT - Version Manager for Fast delivering Teams

Rating: 9 out of 10

Incentivized

October 5, 2019

Use Cases and Deployment Scope

GIT is being used as a version control tool within our organization. Its been used to speed up the code deliveries to different environment and track the changes being deployed to the software product.

GIT being widely used tool has proven itself to be more stable and reliable for code management within organizations and vital for organizations who share their codes(Ex : Integration kits) with their customers IT teams.

Pros

Better tool for products having faster release cycles.
Feature branching is a vital feature available in GIT as it make sure that not all code is merged to the master branch unless its production ready.
Easy to use commands and speed in Git operations.

Cons

GIT Commands could be more natural and intuitive.
GIT should improve handling of files like exe, image, docs etc.
Code commits on multiple branches should be available.

Likelihood to Recommend

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.

Verified User

Engineer in Information Technology (Banking company, 10,001+ employees)

Vetted Review

4 years of experience

Great version control tool

Rating: 10 out of 10

Incentivized

May 5, 2019

Use Cases and Deployment Scope

Git is being used by the whole enterprise right now. We use it as a version control tool to help our developers manage their code version for better collaboration. Our developers love it and have had a great experience with it.

Pros

Easy to use version control.
Pull and push your code without worrying about messing others' codes.
Great support community.

Cons

It's kind of hard to get hands-on.
The Error report is not very specific.
Code conflict resolving can be a pain.

Likelihood to Recommend

If you have a big developing team, you need a version control tool, and Git is the way to go. No other options need to be considered. When the whole team gets used to Git, productivity increases a lot. However, if you are working on your own, Git is still a good tool for managing your code, but its potential will be less appreciated.

Verified User

Engineer in Information Technology (Insurance company, 10,001+ employees)

Vetted Review

3 years of experience

Git it now! If you're working on a small or large team of developers, locally or remotely, you absolutely need to welcome Git to your team.

Rating: 10 out of 10

Incentivized

December 26, 2018

Use Cases and Deployment Scope

Git is being used throughout our organization by the majority of the development teams--custom app development and off-the-shelf customized products. We primarily use Git as a source-code management, a repository, and for revision control and deployment (integrated with other apps to support this function). Being on a large software development team with multiple different developers pitching in on in-house applications, it's essential that we have a tool like Git to manage multiple processes involved with app development. Git allows us to release development changes faster and minimizes potentially negative impacts to our production releases. I also use Git for personal hobby and freelance projects.

Pros

Git allows for collaborative development projects, without worrying about impacting the master revision. By using branches in Git, developers can get a messy as they want, knowing that they can revert to a previous revision.
The ability for co-located and remote teams to develop on a single project independently. From a business perspective, this allows you to strengthen your team by not limiting your employee or team selection processes to a specific geographical location. It also eliminates the requirement for a physical centralized location for co-workers to meet and work.
Git allows for code-comparison so that developers can see what changes they're merging together.

Cons

One of my biggest gripes with Git is the learning curve. Although I am now fairly seasoned, I vividly remember the struggle to learn the ins-and-outs of Git when I first started using it. It has come a long way since I first started using Git, so there are now a lot of fixes to age-old problems, as well as GUI interfaces and 3rd party integrations, eliminating a lot of the initial learning curve for newbies.

Likelihood to Recommend

Git is best suited for storing and managing source code in a local or remote repository. For example, myself and 5 other developer friends are working on a hobby app, but we all work full-time, busy lives, and have no clear deadline in mind to develop this app. Each of us can develop our portions of the app independently on our own time, remotely checking-in our source-code revisions to a centralized repository. As each of us pushes our code to the repository, we can begin to merge the code together into a single revision. Let's say Joe (made up friend name) decides to go a little wild and releases some really experimental code that causes the rest of the app to fail when put into production. Since we used Git, it's easy for us to revert back to a previous release, removing Joe's code changes and fixing the issues with the release.

Chris Martin

Programmer Analyst at Shared Services Canada (Government Administration, 1001-5000 employees)

Vetted Review

10 years of experience

View profile

Git: Version control for the future

Rating: 8 out of 10

Incentivized

December 17, 2018

Use Cases and Deployment Scope

We use Git to manage a truly massive code base. Every developer is added to our enterprise GitHub server and is expected to use it when writing and reviewing code. The problems we try to address with Git include version control and cross team review.

Pros

Code management. This allows us as a team to manage unique code bases for each employee with little to no overhead.
Code backup and versioning. Git truly has the most rebust and reliable code versioning system in the industry.
Handling large amounts of unique data from a variety of teams. We sometimes have to work across teams and across organizations when writing and testing code; Git allows us to do this even when developers are on the other side of the world.

Cons

There is a serious lack of GUI clients for Git.
The command line version of Git is often obtuse and confusing to use.
When something goes wrong in Git, it often does so spectacularly. We spend a lot of man hours cleaning up Git-created messes.

Likelihood to Recommend

Git is super well suited to environments populated by engineers and developers. Git is useful for tracking changes across many people and teams. An environment that Git is not optimal for is management or marketing. Git does not work well with art or promotional materials. The complexity of the tool makes it ill suited for non tech fields.

Verified User

Project Manager in Engineering (Computer Software company, 10,001+ employees)

Vetted Review

6 years of experience

Loading Reviews List....

Git it now! If you're working on a small or large team of developers, locally or remotely, you absolutely need to welcome Git to your team.

Rating: 10 out of 10

Incentivized

December 26, 2018

Use Cases and Deployment Scope

Pros

Git allows for collaborative development projects, without worrying about impacting the master revision. By using branches in Git, developers can get a messy as they want, knowing that they can revert to a previous revision.
The ability for co-located and remote teams to develop on a single project independently. From a business perspective, this allows you to strengthen your team by not limiting your employee or team selection processes to a specific geographical location. It also eliminates the requirement for a physical centralized location for co-workers to meet and work.
Git allows for code-comparison so that developers can see what changes they're merging together.

Cons

One of my biggest gripes with Git is the learning curve. Although I am now fairly seasoned, I vividly remember the struggle to learn the ins-and-outs of Git when I first started using it. It has come a long way since I first started using Git, so there are now a lot of fixes to age-old problems, as well as GUI interfaces and 3rd party integrations, eliminating a lot of the initial learning curve for newbies.

Likelihood to Recommend

Chris Martin

Programmer Analyst at Shared Services Canada (Government Administration, 1001-5000 employees)

Vetted Review

10 years of experience

View profile