Git Reviews & Product Details

It provides version control for codebase files and helps track the modifications made to them. Review collected by and hosted on G2.com.

In my experience, it’s inefficient to store large binary files (such as videos) or a large number of binary files. 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 gives me full control over my code history, makes collaboration easy, and lets me experiment safely through branching and easy rollbacks. Review collected by and hosted on G2.com.

The learning curve can be steep, and when things go wrong like merge conflicts or a messy history it can be confusing to fix without solid Git knowledge. Review collected by and hosted on G2.com.

It use full for version controlling.

Multiple person can work on single file and see their changes.

Merging code of other person so files of repository can update.

Git commits for every update in file of repository.

We can manage multiple version with branching structure. Review collected by and hosted on G2.com.

While merging code sometime get confusion. 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.

Easy version control

Simple collaboration

Reliable change tracking

Fast and efficient

Great for teamwork

Easy branching and merging

Keeps code organized

Stable and dependable Review collected by and hosted on G2.com.

Steep learning curve for beginners

Can be confusing at first

Error messages could be clearer

Complex commands for new users

Merging conflicts can be tricky

Requires practice to master

Not very beginner-friendly initially Review collected by and hosted on G2.com.

Powerful and efficient source control tool Review collected by and hosted on G2.com.

too many commands for a beginner and troubleshooting requires a DevOps engineer Review collected by and hosted on G2.com.

Git has very clear and simple command which can be easily adapted by any new person Review collected by and hosted on G2.com.

Sometime very difficult to revert changes which cause performance issue Review collected by and hosted on G2.com.