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

36 Reviews

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 (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 (10,001+ employees)

Vetted Review

4 years of experience

Using Git for 5+ years

Rating: 10 out of 10

Incentivized

January 30, 2020

Use Cases and Deployment Scope

We use Git in our entire organization for our codebase versioning/management. We migrated from TortoiseSVN. We work in different teams so every team takes the branch from production/master and works in their own branch so that it should not affect any other's work.

Pros

Fastest Branches Switching, in fractions of seconds we can switch between branches.
Easy to pull/push code.

Cons

When some thing went wrong on production, we have to create the revert of the pervious commit, so after fixing the issue we need to revert it again so that the original changes can apply, some times a chain of reverts continue. :(

Likelihood to Recommend

- Easy to clone the repos.
- Secure to keep all the previous history changes.
- Fast to switch between branches.
- Easy to manage the codebase when we are working in the team.

Suleman Ahmad

Senior Software Developer - NodeJS/Express, Angular, MVC Framework in Engineering at CareAxiom (11-50 employees)

Vetted Review

5 years of experience

View profile

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 (1001-5000 employees)

Vetted Review

6 years of experience

Verified on LinkedIn

Git it today

Rating: 10 out of 10

Incentivized

January 20, 2020

Use Cases and Deployment Scope

Git is currently being used for version control in our IT department. This allows us to not only keep various projects under source control, but also to work on many different features concurrently, and maintain many different versions of our software.

Pros

Git has a very small footprint and works seamlessly on all major platforms.
Git's branch management model is wonderful and simple, especially when compared to some other VCS tools I've used.

Cons

Git has no native GUI. This means that if you want a GUI you're reliant on third party software in addition to Git.
Git Repository configuration is done at the host level which makes it difficult to enforce certain requirements, like with Git hooks for example.

Likelihood to Recommend

Git is well suited for any file based scenario where source control is required. We mostly use Git for managing software repositories, but it would also be well suited for document version control. Anything that requires the modification of files and the potential need to roll back to a previous version is a good candidate for Git. The one scenario that in my opinion breaks this rule is database version control. With databases, we manage changes to table structure, functions, stored procedures etc., but I have yet to see good implementation of this with Git.

Ray Smith

Information Technology Manager in Information Technology at The Florida Bar (51-200 employees)

Vetted Review

10 years of experience

View profile

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 (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 (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 (10,001+ employees)

Vetted Review

3 years of experience

Mandatory tool for Software Development

Rating: 9 out of 10

Incentivized

November 23, 2019

Use Cases and Deployment Scope

Our whole company uses Git for code collaboration where a team can continuously develop features for the software. Also, it allows our peers to review the code and once necessary approvals are received, we can merge the code ensuring proper workflow is followed. Git gives us helpful insight regarding project progress, software security vulnerabilities.

Pros

It's a great version control system helps us to develop the software incrementally releasing stable versions.
Git gives proper reminders when ever the my peers requests code review approval.
Git can be easily integrated with other software like Slack, Developer workbenches like Web Storm, Visual Studio Code, etc.
Git commands are very intuitive, makes us to easily understand and get the work done.
Git gives us great insights on the project progress like the number of Pull Requests Raised, Closed Issues, etc.
Git gives an intuitive UI, so the user can operate through the web.

Cons

Git can still improve UI design.
Git can also embed some artificial intelligence, and suggest alternate ways to solve the problem when the code review happens.
Git can also suggest when the deadline for any reviews should be closed so it helps the developers in the team to finish that PR within time.

Likelihood to Recommend

Git is an open-source tool suitable for both small as well as large teams. It's great software for code collaboration and version control. I can't think of any situation where it will be less appropriate.

Verified User

Engineer in Information Technology (201-500 employees)

Vetted Review

4 years of experience

Git - An Absolute Must

Rating: 10 out of 10

Incentivized

November 5, 2019

Use Cases and Deployment Scope

Since the beginning of the uni, I found out that professional companies use at least some kind of versioning system. Git proved to be one of the most robust and logical systems for that. Every single company I have worked for is, or was about to, use it on a daily basis for supporting bigger codebases. The supporting software makes Git even more useful and one of the core tools used for modern software development. This is the number one must-have for every software development job.

Pros

Codebase versioning
Synchronizing multiple programmers on the same codebase
Helps following changes in the codebase, and an easy tool for keeping a stable codebase at all times on local machine and common server

Cons

The .git folder sometimes can mess up a little. We had to reset some repos before because of unstable repository states
I feel like there is still room for improvement for a better code merging tool
CLI outputs sometimes are a bit hard to use, for instance, git log's output is quite ugly

Likelihood to Recommend

For beginner programmers or new recruits in our team, I always recommend to learn how to use Git and integrate it into their projects. This tool is essential for every single software writing process, even if you are the only programmer in the team, or a part of a bigger group. Git is an absolute must. The only scenario where it might not be useful is when people cannot configure it properly and include some unnecessary big files in it.

Balázs Kiss

Software Developer in Engineering at Webvalto Ltd. (51-200 employees)

Vetted Review

5 years of experience

View profile

Loading Reviews List....