Git Reviews & Product Details

We use Git every day as the core of our development workflow. All our codebases are maintained in Git repositories, and our entire team collaborates through feature branches, pull requests, and code reviews. Whenever we ship updates or new releases, we rely on Git to track changes, maintain clean version histories, and make sure every change is reviewed before it reaches production. If a deployment does not behave as expected, we use Git to immediately revert to a stable commit so our systems remain available without downtime. We also use Git to manage long-running features, resolve merge conflicts, and tag releases for better tracking. Git gives our team reliability, clarity, and complete control over the development process, and it is essential for how we build and ship software. Review collected by and hosted on G2.com.

Nothing, there is nothing to dislike about Git Review collected by and hosted on G2.com.

I use Git every single day, so the thing I appreciate most is how easy it is to branch and try stuff without messing up the main code. If I’m working on a feature, I just create a branch, experiment, push it, and merge when it’s stable. The diffs also help a lot, when I’m reviewing my own changes, I can immediately spot if I missed something or added a random debug log. Review collected by and hosted on G2.com.

Literally no cons apart from the weird pop up comes while resolving and merging the conflicts Review collected by and hosted on G2.com.

I feel every software has to use git. Because it maintains the history of workflows and helps multiple people work on same project. It is easy to use and implement. I frequently use it in all my projects to track progress. It has various features like rollback and history of commits to show differences. It integrates easily with all products and customer support and community is great in supporting with issues at hand. Review collected by and hosted on G2.com.

It could be difficult for beginners working on large scale enterprise projects with multiple developers involved and face difficulty with issues like merge conflicts. Review collected by and hosted on G2.com.

Git ensures efficient and reliable version control. Versioning becomes simple for developers using Git. Developers can experiment without any risks using branching and merging techniques in Git. Git is compatible with tools like GitHub or GitLab. Git has a powerful command line interface. Overall, it facilitates developers in ensuring code quality and easy collaboration. Review collected by and hosted on G2.com.

The curve of learning is steep in this case. This is especially because it involves command-line work. This is especially problematic for new users. Sometimes, there are merge issues that have to be handled. This is sometimes tricky. The improper use of certain commands is also to be kept in mind. Review collected by and hosted on G2.com.

For me, Git’s greatest strength lies in its ability to combine flexibility with reliability. As a distributed version control system, it allows each developer to maintain a complete copy of the project history locally, which not only accelerates workflows but also minimizes dependence on a central server. Its lightweight branching and merging make it easy to experiment, so feature branches, hotfixes, and pull request-based reviews fit seamlessly into team routines. The detailed commit history serves as an auditable and searchable log of changes, aiding in debugging, code reviews, and the transfer of knowledge. When you add Git’s extensive tooling and integrations—such as CI/CD pipelines, code review platforms, hooks, and the powerful command-line interface—it becomes clear why Git is suited for everything from individual projects to large, cross-functional teams. All in all, it’s robust, fast, and essential for modern software development. Review collected by and hosted on G2.com.

Git is powerful, but a few things frustrate me:

Steep learning curve & confusing concepts — staging, rebasing, and detached HEAD are easy to get wrong without practice.

Cryptic CLI errors — error messages aren’t always helpful, which makes debugging Git issues time-consuming.

Merge conflicts — resolving complex conflicts (especially across large refactors) can be error-prone.

History rewriting risks — commands like' git rebase' or' git push --force' can accidentally lose work if not used carefully.

Poor handling of large binary files — repositories with big binaries grow fast unless you use Git LFS.

Submodules and monorepos — they add considerable operational complexity.

Mitigations I use: training + docs for teammates, protected branches and PRs, git-lfs for binaries, clear branching policies, GUI tools for conflict resolution, and automation (CI) to catch mistakes early Review collected by and hosted on G2.com.

I like using Git for development and code management, especially when more than two developers are working together. I appreciate the branch management feature, which is very beneficial for my work. Git is a good tool for managing code in a repository. Additionally, it's very easy to initiate Git and set it up in projects globally, making it straightforward to get started. Review collected by and hosted on G2.com.

merge conflict, it's tedious task if we are working on same file Review collected by and hosted on G2.com.

Git’s best trait is that it never loses your work. Branching is cheap, merging is flexible, and the whole system pushes you toward clean, traceable changes. It’s a safety net with a time machine attached. Review collected by and hosted on G2.com.

What I don’t enjoy is how easily Git lets you shoot yourself in the foot. A wrong reset or force-push can turn your stomach. The command set also feels like archaeology—powerful, but full of weird historical edges. Review collected by and hosted on G2.com.

What I like most about Git is its ability to track every change in a project with precision, making it easy to collaborate and roll back to previous versions when needed. Its branching and merging features allow multiple people to work on different parts of the code simultaneously without conflicts, and the distributed nature ensures I always have a complete local copy of the repository. This flexibility, combined with powerful integration options, makes it an indispensable tool for any development workflow. Review collected by and hosted on G2.com.

What I dislike about Git is that it can be intimidating for beginners due to its command-line complexity and the variety of commands to learn. Resolving merge conflicts can sometimes be confusing, especially in large projects, and remembering less frequently used commands often requires looking up documentation. Review collected by and hosted on G2.com.

I really appreciate that Git is very light and makes it easy to record my code fetch. The user interface is very easy to use, which I find quite helpful. Setting it up was also straightforward with just a one line command in the terminal. Review collected by and hosted on G2.com.

nothing as such Review collected by and hosted on G2.com.

I like its simplicity and easy to use and speed, git never hangs, very easy to install and integratre with other tools like VS code Review collected by and hosted on G2.com.

No issue I found all perfect in this toll Review collected by and hosted on G2.com.