Skip to main content
TrustRadius
Git

Git

Overview

Learn from top reviewers

The cornerstone of collaborative development

Rating: 10 out of 10
January 5, 2024
IncentivizedVetted ReviewVerified User
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...
Continue reading
Gabriel Freire
Engineer - Information Technology
Senior Staff Engineer
Equinix
Git9 years of experience

Git has everything you need for code

Rating: 9 out of 10
June 28, 2021
IncentivizedVetted ReviewVerified User
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 progra...
Continue reading
Verified user
Employee
Git4 years of experience

Using Git for 5+ years

Rating: 10 out of 10
January 30, 2020
IncentivizedVetted ReviewVerified User
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 prod...
Continue reading
Suleman Ahmad
Engineer - Engineering
Senior Software Developer - NodeJS/Express, Angular, MVC Framework
CareAxiom
Git5 years of experience

Git is the VCS King

Rating: 10 out of 10
January 23, 2020
IncentivizedVetted ReviewVerified User
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 co...
Continue reading
Josh Stapp
Engineer - Engineering
Sr. Drupal Developer
ICF Next
Git6 years of experience

Git it today

Rating: 10 out of 10
January 20, 2020
IncentivizedVetted ReviewVerified User
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...
Continue reading
Ray Smith
Professional - Information Technology
Information Technology Manager
The Florida Bar
Git10 years of experience

Every developer should be using Git

Rating: 10 out of 10
January 18, 2020
IncentivizedVetted ReviewVerified User
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 ...
Continue reading
Nate Dillon
Engineer - Information Technology
Front-End Web Developer, Office of Mediated Education
Kansas State University
Git8 years of experience

Easy to use and collaborate

Rating: 6 out of 10
January 18, 2020
IncentivizedVetted ReviewVerified User
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 ...
Continue reading
Verified user
Engineer
Git5 years of experience

Git: Branches are cheap, damn cheap

Rating: 10 out of 10
December 19, 2019
IncentivizedVetted ReviewVerified User
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...
Continue reading
Verified user
Engineer
Git3 years of experience

Mandatory tool for Software Development

Rating: 9 out of 10
November 23, 2019
IncentivizedVetted ReviewVerified User
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 necess...
Continue reading
Verified user
Engineer
Git4 years of experience

Git - An Absolute Must

Rating: 10 out of 10
November 5, 2019
IncentivizedVetted ReviewVerified User
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 system...
Continue reading
Balázs Kiss
Employee - Engineering
Software Developer
Webvalto Ltd.
Git5 years of experience

GIT - Version Manager for Fast delivering Teams

Rating: 9 out of 10
October 5, 2019
IncentivizedVetted ReviewVerified User
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 deploye...
Continue reading
Verified user
Engineer
Git4 years of experience

Don't lose a line of work, Git it backed up.

Rating: 10 out of 10
September 28, 2019
IncentivizedVetted ReviewVerified User
Git is used across most of the organization, if not all of it. Git is a Version Control System, which means that allows you to "backup" and control who edited your files, prov...
Continue reading
César Costas Carrera
Employee - Information Technology
FrontEnd Web Developer
loveholidays
Git3 years of experience

Great version control tool

Rating: 10 out of 10
May 5, 2019
IncentivizedVetted ReviewVerified User
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 develop...
Continue reading
Verified user
Engineer
Git3 years of experience

The version control system you need!

Rating: 9 out of 10
March 30, 2019
IncentivizedVetted ReviewVerified User
Git is one of the source code version control tools used at my organization. We are using Git (Gitlab) to store our source code across multiple repositories. We have a mainlin...
Continue reading
Nikolay Rogoshchenkov
Engineer - Engineering
R&D Project Engineer
Innovative Scientific Solutions Inc
Git5 years of experience

Git things done

Rating: 9 out of 10
February 12, 2019
IncentivizedVetted ReviewVerified User
In our organization, Git is used by several departments for file versioning, collaborative work on the same source code, change tracking, branch merging, version comparison et...
Continue reading
Cristian Bodnarasec
Manager - Information Technology
Senior Software Development Manager
eSilicon
Git3 years of experience
Log in with LinkedIn to see content from your network

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons
Gabriel Freire
Senior Staff Engineer
Equinix (Computer Software, 10,001+ employees)
Return to navigation

Pricing

View all pricing
Git

Git

N/A
Unavailable

Sorry, this product's description is unavailable

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

5 people also want pricing

Alternatives Pricing

GitHub

GitHub

$4
per month per user
What is 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…

Redgate Flyway

Redgate Flyway

Free
What is Redgate Flyway?

Flyway, by Redgate, automates database deployments across teams and technologies. It is a database devops solution that is used to accelerate software delivery and ensure quality code.

Return to navigation

Product Demos

Git Merge and Rebase Demo

YouTube

Git hooks, practical uses (yes, even on Windows)

YouTube

Git Tutorial For Beginners | What is Git and GitHub? | Git Tutorial | DevOps Tutorial | Simplilearn

YouTube

Git Push Command | Git Bash Tutorial | Git Commands | Git Tutorial For Beginners | Simplilearn

YouTube
Return to navigation

Product Details

What is Git?

Git Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(73)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

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.

Users commonly recommend learning Git thoroughly to utilize its benefits for code repository management, version control, and team collaboration. They emphasize the importance of utilizing the command line interface and following established processes for branching and merging. Users also encourage exploring advanced features, seeking support from online resources like Stackoverflow, and considering other alternatives if needed. Overall, users consider Git to be an essential tool with excellent features and community support in the software development realm.

Reviews

(1-25 of 36)
Companies can't remove reviews or game the system. Here's why

The cornerstone of collaborative development

Rating: 10 out of 10
Incentivized
January 05, 2024
GF
Gabriel Freire
Senior Staff Engineer
Equinix (Computer Software, 10,001+ employees)
Vetted Review
Verified User
Git
9 years of experience
View profile
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.<br>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 and Cons
  • Version Control
  • Conflict Resolution
  • Collaborative Work
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.

Git has everything you need for code

Rating: 9 out of 10
Incentivized
June 28, 2021
Verified User
Vetted Review
Verified User
Git
4 years of experience
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 and Cons
  • 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
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.

Using Git for 5+ years

Rating: 10 out of 10
Incentivized
January 30, 2020
SA
Suleman Ahmad
Senior Software Developer - NodeJS/Express, Angular, MVC Framework
CareAxiom (Computer Software, 11-50 employees)
Vetted Review
Verified User
Git
5 years of experience
View profile
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 and Cons
  • Fastest Branches Switching, in fractions of seconds we can switch between branches.
  • Easy to pull/push code.
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.

Git is the VCS King

Rating: 10 out of 10
Incentivized
January 23, 2020
JS
Josh Stapp
Sr. Drupal Developer
ICF Next (Computer Software, 1001-5000 employees)
Vetted Review
Verified User
Git
6 years of experience
View profile
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 and Cons
  • Better merges than anything else.
  • Logging.
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.

Git it today

Rating: 10 out of 10
Incentivized
January 20, 2020
RS
Ray Smith
Information Technology Manager
The Florida Bar (Legal Services, 51-200 employees)
Vetted Review
Verified User
Git
10 years of experience
View profile
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 and Cons
  • 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.
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.

Every developer should be using Git

Rating: 10 out of 10
Incentivized
January 18, 2020
ND
Nate Dillon
Front-End Web Developer, Office of Mediated Education
Kansas State University (Higher Education, 5001-10,000 employees)
Vetted Review
Verified User
Git
8 years of experience
View profile
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 and Cons
  • Source control
  • Collaboration
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.

Easy to use and collaborate

Rating: 6 out of 10
Incentivized
January 18, 2020
Verified User
Vetted Review
Verified User
Git
5 years of experience
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 and Cons
  • Flexibility
  • Version history
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.

Git: Branches are cheap, damn cheap

Rating: 10 out of 10
Incentivized
December 19, 2019
Verified User
Vetted Review
Verified User
Git
3 years of experience
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 and Cons
  • Fast.
  • Robust.
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.

Mandatory tool for Software Development

Rating: 9 out of 10
Incentivized
November 23, 2019
Verified User
Vetted Review
Verified User
Git
4 years of experience
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 and Cons
  • 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.
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.

Git - An Absolute Must

Rating: 10 out of 10
Incentivized
November 05, 2019
BK
Balázs Kiss
Software Developer
Webvalto Ltd. (Banking, 51-200 employees)
Vetted Review
Verified User
Git
5 years of experience
View profile
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 and Cons
  • 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
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.

GIT - Version Manager for Fast delivering Teams

Rating: 9 out of 10
Incentivized
October 05, 2019
Verified User
Vetted Review
Verified User
Git
4 years of experience
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 and Cons
  • 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.
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.

Don't lose a line of work, Git it backed up.

Rating: 10 out of 10
Incentivized
September 28, 2019
CC
César Costas Carrera
FrontEnd Web Developer
loveholidays (Recreational Facilities and Services, 201-500 employees)
Vetted Review
Verified User
Git
3 years of experience
View profile
Use Cases and Deployment Scope
Git is used across most of the organization, if not all of it. Git is a Version Control System, which means that allows you to "backup" and control who edited your files, providing its best value when it comes to plain text files, such as code.
Pros and Cons
  • Git is a distributed system. Usually adding the word "distributed" makes things very complex and messy, but not with Git, thanks to its branches and merge control.
  • It's insanely fast.
Likelihood to Recommend
Git is the best suitable tool whenever you need to backup your documents quickly. Even more so if you need to keep track of who made changes.

It is not suitable when you want to work in a "blocking" mode, meaning:
- blocking any other user from editing while another user is editing.
- setting editing permissions per file avoiding users to edit or read a specific file.

Great version control tool

Rating: 10 out of 10
Incentivized
May 05, 2019
Verified User
Vetted Review
Verified User
Git
3 years of experience
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 and Cons
  • Easy to use version control.
  • Pull and push your code without worrying about messing others' codes.
  • Great support community.
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.

The version control system you need!

Rating: 9 out of 10
Incentivized
March 30, 2019
NR
Nikolay Rogoshchenkov
R&D Project Engineer
Innovative Scientific Solutions Inc (Aviation & Aerospace, 51-200 employees)
Vetted Review
Verified User
Git
5 years of experience
View profile
Use Cases and Deployment Scope
Git is one of the source code version control tools used at my organization. We are using Git (Gitlab) to store our source code across multiple repositories. We have a mainline development branch which all our new code is eventually pushed to after being code reviewed by their branch using pull requests.
Pros and Cons
  • Ability to create branches and merge those changes in.
  • Diff-ing changes.
Likelihood to Recommend
Developers can work parallel on projects, increasing the speed at which teams can work, thus causing projects to complete faster. Git has saved our organization hours of having to manually trace code to a breaking change or manage conflicting changes.

Git things done

Rating: 9 out of 10
Incentivized
February 12, 2019
CB
Cristian Bodnarasec
Senior Software Development Manager
eSilicon (Semiconductors, 501-1000 employees)
Vetted Review
Verified User
Git
3 years of experience
View profile
Use Cases and Deployment Scope
In our organization, Git is used by several departments for file versioning, collaborative work on the same source code, change tracking, branch merging, version comparison etc. Especially because we have distributed teams all over the world, we needed a reliable tool to achieve these goals, and Git was the natural choice.
Pros and Cons
  • File versioning - easy to see the history of the changes.
  • Collaborative work on the same source code -- by providing the ability to create branches.
  • Merging branches and comparing versions made easy.
  • It is free and open source.
  • Git is so popular that when hiring, it is easy to find developers who already know this.
Likelihood to Recommend
Git is suited for doing source code versioning of all-size projects, from small to large and very large. Does very well when you have distributed teams, as it increases the team's focus, collaboration, decreases the time needed for merging code and finding differences between file versions, and decreases the time needed to make a software release. Therefore, the time to market of new projects or new features is improved (any top manager's desire).

Git: a solid version control tool

Rating: 9 out of 10
Incentivized
February 04, 2019
Verified User
Vetted Review
Verified User
Git
6 years of experience
Use Cases and Deployment Scope
Git is our core version control tool in my company and it is used not only in our development department but in multiple other departments like Tech Writing and Implementation. In development, we use Git to track our development changes and to organize our release cycles with different branches to track our stages. We utilize tools that integrate with Git like Bitbucket to have a front end UI that helps us manage things like pull requests, which are branches off of QA for development changes we would like to add to release. Git is the core infrastructure in what we do here and I have been using it every day for the past 6 years.
Pros and Cons
  • Ability to create branches off current releases to modify code that can be tested in a separate environment.
  • Each developer had their own local copy of branches so it minimizes mistakes being made.
  • Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
  • Conflicts are displayed nicely so that developers can resolve with ease.
Likelihood to Recommend
Git is well suited for development, for tracking code changes in files, creating branches off projects to create pull requests that get merged back in, etc. It is used for anything we want to track on a computer like Source code, SQL scripts, documentation (Html/PDF/word docs), and project files for applications. Not really appropriate for backing files up just to have a backup, google drive is a better option for that.

Git - Best Source Control Management Tool

Rating: 10 out of 10
Incentivized
January 16, 2019
GS
Gabriel Samaroo
Senior Software Engineer
Rocketrip (Computer Software, 11-50 employees)
Vetted Review
Verified User
Git
6 years of experience
View profile
Use Cases and Deployment Scope
My organization uses Git for version control of our various codebases. It is used by the engineering and dev-ops teams. We use git because it reliably handles creating branches for various features and bug fixes, and provides an effective and trusted way to merge and release that code to our different environments.
Pros and Cons
  • Ability to create branches and merge those changes in - very cleanly and in an organized way. Other features such as cherry-picking and rolling back are extremely useful.
  • Diff-ing changes is a great utility for reviewing code and understanding the history of code changes.
  • Git makes working in teams on the same set of code very possible, compared to some of the alternatives like SVN.
Likelihood to Recommend
Git is by far the best Source Control Management Tool I've used. I would recommend it to anyone, whether it's an individual working on their own project, a small start-up company, or a huge organization with thousands of developers. Maintaining code via source control is absolutely mandatory for all developers everywhere.

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
CM
Chris Martin
Programmer Analyst
Shared Services Canada (Government Administration, 1001-5000 employees)
Vetted Review
Verified User
Git
10 years of experience
View profile
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 and Cons
  • 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.
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.

Git: Version control for the future

Rating: 8 out of 10
Incentivized
December 17, 2018
Verified User
Vetted Review
Verified User
Git
6 years of experience
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 and Cons
  • 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.
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.

Git is best to cooperate with customers

Rating: 9 out of 10
Incentivized
December 17, 2018
JW
Jakub Wilk
President & Co-Founder
Enovatio (Computer Software, 1-10 employees)
Vetted Review
Verified User
Git
4 years of experience
View profile
Use Cases and Deployment Scope
Git is used as alternative solution to mercurial. It is used more by my department and is used to manage projects for customers. We are using them in the cloud version to share code with our customer. Each team has their own repository per customer. We usually receive this repository from the customer, because he wants to have control over this.
Pros and Cons
  • Cooperation with customer
  • Integration with visual studio
  • Distribution
  • Branching
Likelihood to Recommend
Git is suited very well for programmers and less for new programmers that are mouse oriented. it gives very good support as visual studio tool and I think that thanks to this it is used very often within the Microsoft community. I'm very much MS oriented so my perspective is different than the others and I heard that the world is not only MS. In our company it is very well suited within offshoring projects to share and distribute source code around countries and companies.

Versioning and branching at their best

Rating: 10 out of 10
Incentivized
December 14, 2018
Verified User
Vetted Review
Verified User
Git
2 years of experience
Use Cases and Deployment Scope
We use Git across all of our development projects in order to work on multiple aspects at once and then merge branches as needed. There are four scrum teams and one Kanban team that handles hardware issues. All the scrum teams are developing and maintaining software to various degrees across the organization.
Pros and Cons
  • It's the best at version control that I've seen. Rollbacks are a snap.
  • Provides local control down the individual developer level, which in turn allows easy management back up the chain of command.
  • Cloning is perfect when you need to copy a project to tweak it without messing with the main branch.
Likelihood to Recommend

For any code commitments from any individual developer of any talent range it's awesome. Getting the hang of it happens over time (and can be speeded up if a senior person looks over your shoulder and gives you pointers). This comes into play for testing feature sets and ensuring branches are merged correctly.

For teams where many developers are working on a single project, Git allows them to all work on the same code without messing up back end work in the process. For any bugs or defects that slip through (big ones, I mean), it's super easy to roll back to an earlier version and call it good.

Git With the Program: Superior Codebase Management

Rating: 10 out of 10
Incentivized
November 29, 2018
JT
Joel Tanzi
Software Engineer
Lockpath, Inc. (Computer Software, 51-200 employees)
Vetted Review
Verified User
Git
4 years of experience
View profile
Use Cases and Deployment Scope
Our organization uses Git for code versioning, namely to track and manage changes to the codebase in a way that avoids accidentally writing over another engineer's code, resolves change conflicts, and provides a rollback option in the event of a breaking change. Git has become an important part of the development workflow for most software engineering teams. The problem Git addresses for us is the problem of having multiple people updating a codebase. One developer might change a portion of the code in one area and another might change it somewhere else, and managing the merging of these changes together is the main job of Git. To facilitate this Git stores every committed change in a log, and this log can be reviewed and even used to roll the code back and reject changes further down the pipeline. In our organization, each engineer creates a new branch from the master codebase whenever they are starting a new task in the project, and once they have completed that task and confirmed the code is stable, the code can be merged into the master codebase and eventually included in the production build. Our team has a strict policy of not merging your own code, so the code is reviewed and approved by another engineer whom merges it in after assessing its impact. We use Git across our engineering department only.
Pros and Cons
  • Git manages the merging of changes from different team members and provides for a way to roll back those changes when necessary.
  • Git allows for management of multiple branches of a code project and merging them in through a controlled and considered manner.
  • Git provides a complete history of all code changes and who made them, making the process of identifying when breaking code came in a much easier one along with identifying the code to roll back to (when needed).
  • Git is a powerful tool for change management and avoiding breaking code making its way into production.
Likelihood to Recommend
Git is very well suited for teams of software engineers who are collaborating on a software project. It makes life much easier for project managers, team leads and software architects to make decisions about which code to allow in and which to send back to the drawing board. It can also be a good tool for solo developers to use to manage and showcase their codebase and is, in fact, the versioning system on which the most popular code hosting platform, GitHub, is built on.

Git has at times been used for less technical content such as document management, but this may be a less appealing tool for non-technical professionals such as writers, whom may not want to deal with its learning curve and may find tools built into MS Office or Google Drive to be sufficient to manage document versions.

Git is the king for a reason

Rating: 10 out of 10
Incentivized
September 12, 2018
Verified User
Vetted Review
Verified User
Git
7 years of experience
Use Cases and Deployment Scope
Git is being used by our organization on an information technology department level. We use Git as our sole Version Control system for all of our software releases, maintenance & deployment.
Pros and Cons
  • Git is designed to work in a distributed manner, allowing each developer to run a local node that has full control of the project. Through this, the developer is able to merge his work with others on a main 'branch' & work in sync without having to worry about stepping on your other developers toes.
  • Because Git has solved the software problem of dependency, users who commit code that needs to be deleted can just roll back to a restore point, saving precious development time & tons of headaches for Information Technology. This is also very helpful when cloning projects or creating new features on the current project.
  • Git has a beautiful command line interface that is intuitive, easy to learn & extensible. You can also observe all the changes you have made in your project throughout the development with just a few simple commands. This diverse set of command-line tools is easy for the end user & very powerful.
Likelihood to Recommend
Git is a great tool, in fact, possibly the best tool to use when keeping track of all the projects through version control. Through its rigorous program, it allows the end user to see how code behaves before being merged into the main branch, and allows the intelligent user to avoid problems & fix them if necessary. It is easy to learn the common verbiage (clone, add, commit, pull & push) but at the same time have all advanced features that you can need in a future (merge, cherry pick, diffs ...) It is faster than other version control solutions currently on the market, & because it's open source it's just the best go-to for Version Control Software.

Open source, widely used, reliable, but medium-high technical learning for effective use

Rating: 9 out of 10
Incentivized
August 29, 2018
Verified User
Vetted Review
Verified User
Git
2 years of experience
Use Cases and Deployment Scope
Git is mainly used in my organisation by the technical team who are mainly responsible for project delivery. It provides us with an avenue for version control and code management. It addresses the risk of time and effort loss during project implementation.
Pros and Cons
  • Version control and backups
  • Branching and merging
  • Open source
Likelihood to Recommend
Very suitable for the project implementation stage, where version control is required. It is more suitable for files that mainly involve text formatting for change/version tracking. It is less appropriate in situations where entire files change rapidly on each commit (e.g. image/graphic design files). Git is less suited for management personnel.

GIT is a gift!

Rating: 8 out of 10
Incentivized
June 15, 2018
Verified User
Vetted Review
Verified User
Git
5 years of experience
Use Cases and Deployment Scope
GIT is used as a server out of the box. It is being used by the whole organization. Dedicated Git server software helps, amongst other features, to add access control, display the contents of a Git repository via the web, and help managing multiple repositories.
Pros and Cons
  • Unlike centralized version control systems, Git branches are cheap and easy to merge. This facilitates the feature branch workflow very user-understandable.
Likelihood to Recommend
Staging area: Make sure your commits have logically grouped changes and not everything else you are working on.
Return to navigation