Skip to main content
TrustRadius
Git

Git

Overview

Recent Reviews

TrustRadius Insights

Git is a widely used version control system that offers a range of use cases for different teams and organizations. Engineering and …
Continue reading

Git it today

10 out of 10
January 20, 2020
Incentivized
Git is currently being used for version control in our IT department. This allows us to not only keep various projects under source …
Continue reading
Read all reviews

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
Return to navigation

Pricing

View all pricing
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

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…

What is Liquibase?

Liquibase is a database change management tool that helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database…

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

Git Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(74)

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.

Attribute Ratings

Reviews

(26-36 of 36)
Companies can't remove reviews or game the system. Here's why
Joshua Weaver | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Git manages the source control over all of our web-related codebases. It allows us to be light and flexible with our approach to not only development and coding, but also using a continuous integration workflow that automates processes in the deployment chain. Without Git, life as a developer would be quite painful indeed.
  • It handles many of the complicated features of version control for you like merging branches
  • It has a diverse ecosystem of tools that utilize its many features
  • Documentation for Git and its workflows can be quickly found and understood
  • Some of the commands are a little obtuse if you're not using a Git Client
  • Since Git is so widely used in the development space, it's easy to believe that growth and innovation might become stale in the area of version control. Competition is sparse these days and I'm curious if this "Standard" is going to keep moving forward somehow.
  • It's hard to fault a tool that is so ubiquitous and hardly gets in your way.
If you're developing any software that requires the need of keeping the source code around, then you should be using Git. The only time I can think of an instance where I might suggest not using Git is when you deal with an integrated and closed development environment where the source code is tightly held and managed within the IDE or environment itself. This type of development is rare these days but does still exist. As such, it would take extra measures to extract the source code out of the environment to then be able to utilize the benefits of Git.
Everyone else should utilize Git because it helps in many aspects of Source Control, for example:
  • Feature Branches during development
  • Forking entirely new versions of projects
  • Merging changes
  • Reviewing Commit histories and changes
  • Rolling back changes
Miguelangel Nuñez | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Git is only used in our department. All our code is saved and versioned with Atlassian Stash using Git as version control system. There are at least 15+ projects in the development using this VCS.
  • Git branches allow you to work with different features at the same time.
  • Git makes programming easy and fun. You can share your code with a team peer or an entire community. You can modify the same file because you're working with local changes instead of a centralized repository.
  • At first, it's difficult to learn all the concepts, (rebase, merge, forking). They are conceptually difficult aspects to get in at first sight. You can use a graphic UI to handle it more easily.
I think you can use Git for every project you have, there aren't limitations about a kind of program or something specific. It's more about personal preferences and ease of use.
David Petrie | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Git is one of the source code version control tools used at my organization (the other major one being Subversion). We are using Git to store our source code across multiple repositories and branches (features and bugs). 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. The development branch in our Git repositories are polled for any changes, and builds are automatically run to verify the code.
  • Branching
  • What I find as the main benefit of Git is the ease that branches can be created in a repository - whether that's for working on new features or to fix bugs. It's as easy as selecting the code you want to branch from and "git checkout -b newBranch". Mainly I use this for branching from our development branch (also known as trunk) and once the code is finished, we merge the branch back into the development branch. Switching branches in Subversion is a little bit more complex, whereas Git is super easy to use.
  • Pull Requests
  • Pull requests can be created on a repository allowing code to be reviewed before being merged to the main branch. External tools like Bitbucket can be used to integrate into the Git repositories, allowing users to easily review and comment on your pull requests.
  • Local Repositories
  • When you use Git, you checkout the repository to your machine locally - and any commits that you make only affect your local repository, rather than the "real" repository at a remote location. This allows you to commit often and finalize all of your code before merging onto the latest development branch.
  • Understanding
  • Git has a little bit more of a learning curve when compared to other source control solutions, e.g. Subversion - but this is due to the more complex features it offers.
  • IDE Support
  • There aren't as many plugins for Git when compared to other source control solutions. Subversion has better plugins for IDEs and seems to be well supported.
  • Git Bash
  • Using Git bash, or the GUI that comes with Git can be slightly daunting at first. Tools like SourceTree are a solution to this problem, as they run the underlying Git commands for you.
Git is perfect for any micro-repository solutions, as it can checkout source code quickly and switch between branches easily. For example, let's say you have a new feature to add to a microservice your working on, a feature branch can be created quickly, and the working copy can be automatically switched to that new branch. If you ever need to share your code to a wider public audience, Github is great for this. Anyone with an account can check out and comment on your code and suggest changes. Also, Git is free!

As for a scenario where you wouldn't want to use Git, I've heard that Git can struggle with image files (jpg, gif) sometimes, so users with lots of images may want another solution.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Git is used by my department and it is what we used to store and track all of our development projects. For any projects that require some type of programming, Git is used in order for us to maintain and update our code. Git allows us to easily share and manage our project all in one area.
  • Git does a fantastic job of tracking changes within your code. You can see all of your previous versions and it allows you to see easily who made the changes and when the changes were made.
  • Git allows you to revert your changes to current versions or commits should your project need to go back to how it behaved in the past.
  • Git does a great job of allowing multiple developers to work on one project by creating different branches within your git project.
  • Git may take some time to get grasp if you have never used it before in your development process. It can be intimidating to try to learn at first.
  • Git has some strange behaviour of autocrlf in Windows.
Git is great for keeping track of your project when multiple developers are in the picture. This will allow you to see all the changes within the project and contributions of all of the developers and prevent overwriting of each other's code. Another great use for Git is creating multiple environments. For instance, having a staging environment that would allow you to see how your code behaves before merging your new code into your production environment.
March 07, 2018

Git gets it.

Benjamin Hale | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We currently use Git to track all changes in our multiple websites and landing pages, along with internal scripting projects. Git addresses the issue of keeping track of the code we have created, and maintains security and redundancy between employees. In this way, we can be sure that no one person or one device has all the information we use daily to keep our systems and websites running.
  • Git works quite well to keep a record of the code and the changes made on code for our websites and internal scripting.
  • Git allows multiple developers to work on a single project with the checkout process.
  • Git allows us to track who makes edits, when they were made, and how we can go back and fix any mistakes or bugs.
  • Git is FAST!
  • Git can be slow to learn, and much of it is done through the command line.
  • Git is a single solution for a code repository, so if you are looking for larger scale backup or documentation, it might not be the right fit.
Git is great for coding for individuals and teams. The ability to have versioning and how git is built into many development tools helps to make using one of the many git repository services easy. I can imagine that for some projects, there are better solutions for keeping code, but for most situations, git works well.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We are currently using Git for all of our marketing websites. We're using it to save versions of code as a backup, to track changes and to see when changes were made and by whom. It helps us track updates for our clients and enables our team to work on the same sites concurrently.
  • Code backups
  • Code tracking
  • Branching
  • Team development
  • Git has a learning curve
Git is amazing at helping teams of developers collaborate on sites. It allows them to work at the same time by utilizing branches, then merging in with the main branch. It allows developers to track their code and submit bug requests as well as comments on bug fixes.
March 01, 2018

The Awesome Git

Christy Herron | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
I am a freelance, full-stack, software developer. Git repositories are used for all my code. I use multiple machines to create software for different platforms - Ubuntu to create websites to run on Heroku, and iOS apps. Git allows me to work on any machine while away from my normal setup. It also keeps all my source code backed-up, and I have the ability to grant access to my client if required.
  • Backup. It's the cheapest and easiest backup solution I've found in 20 years of coding. If/when a machine goes down I know I have no issues with losing work.
  • Access. I can access my code on any machine, anywhere I need to be. If I find myself with some spare time, and any machine at hand, I can dive in and carry on working.
  • Forking. It's very easy to fork new ideas without losing the current development thread.
  • I mainly use xCode and SublimeText, both of which provide a number of useful commands to backup my code to git. I'd like to see further integration, perhaps automated.
Developers often work in pairs, and on multiple projects at once. Sharing code across multiple machines can be very difficult. I don't know how we did it before Git came along - well, I do, but it wasn't pretty! Git has been a lifesaver on many occasions when systems have gone down due to hard drive failure. Git has also made it possible for me to manage and monitor the input of remote developers, as I can see in the commit logs for each push to the repositories.
February 15, 2018

A must have

Score 10 out of 10
Vetted Review
Verified User
Incentivized
I use it for all my projects both professionally and personally. Version control is a must have for development and Git has served me well.
  • Great CLI
  • Great documentation
  • Great support community
  • There are nuances to some of the commands that new users might trip up on such as fetch vs. pull
It’s well suited for any coding project where versioning is important. Cannot think of a good reason to not use it.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use git across our entire organization. We used to use SVN back in the day, but switching to Git has made our lives so much better. Ease of use is excellent and it's a much cleaner approach to version control.
  • Distributed versioning. Being able to have each developer working on their own stuff without stomping on each others' changes is very important.
  • Incremental versions are very crucial to proper development.
  • It's so much faster than SVN. You can check out a repo in probably 10% of the time it took using SVN.
  • There is no official UI for git, so you need to be somewhat familiar with the command line.
  • Undoing a merge could be made easier, but there are definitely complications in allowing something like that.
If you are doing any sort of software development, you need to be using Git.
December 14, 2017

Better choose Git!

Rene Enriquez | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We are using Git to store our source code with all of our clients. All the technical staff uses Git as a CVS. It's an awesome product for versioning and managing source code no matter what programming language you use.
  • Versioning
  • Revision of newly implemented code by using Pull Requests
  • Branches to allow developer working in different features at the same time
  • Good integration with CI and CD tools
  • A lot of plugins and tooling are available to be integrated with Git
  • Not sure, it has been working awesome to solve our needs and there is a lot of documentation available to meet the product. As you study features you discover ways to use them.
Even if you have only one developer working on a project it is always a good idea to use a CVS like Git to version the source code. Not sure where it shouldn't be used.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Git for many varying purposes. The most obvious use case is for our code-based projects. Drupal modules, WordPress plugins, Composer packages, NPM modules, you name it--it's all in GitHub! Additionally, we use GitHub for managing libraries of shared code snippets, managing configuration files, holding Ansible playbooks, and the list goes on and on.
  • Version control just about anything!
  • Manage the code of projects both large and small
  • Manage configuration
  • Facilitate easy collaboration between developers
  • Sometimes Git can be daunting to use, especially if you are new to it, and especially if you're on the command line.
  • Many Git clients exist, but it would be great if Git had an official cross-platform desktop application. However, many alternative Git desktop applications exist.
Git is suited to almost any purpose where you have some code that you want to keep somewhere, or you have some files you want to maintain a history of changes of. The only thing Git is not really well suited for is storing or version controlling large binary files.
Return to navigation