Git Reviews & Product Details

I like it sort of industry standard to control versions of different files so once we have a grasp of the concepts all the terminology and commands are ready for whatever learning curve initiative but once you know what you're doing straightforward to use and it's it's actually the only tool of use to do source control but I used it for my documentation and also the software developers do it for their versions of the software so between two of us would be following the same principles and the UI is relatively lightweight for my use anyway Review collected by and hosted on G2.com.

I think the initial on boarding and the steep learning curve is a little bit off putting at first it took me quite a while to sort of get my head around the concepts and the fact that you need to remember the different commands and typing them in isn't really that intuitive if there was some way that it could give you a reference list and why that would just be helpful for people that aren't those comfortable views it's not something else every day and I tend to have to refresh my memory each time I go in and it would just make that process a bit easier Review collected by and hosted on G2.com.

What I like most about Git is the sense of control it gives while working on code. Every change is tracked, so I never have to worry about losing progress or breaking something permanently, I can always roll back if needed. Branching is another huge advantage, as it lets me experiment or work on features independently without affecting the main codebase. Review collected by and hosted on G2.com.

One thing I don’t like about Git is that it has a bit of a learning curve, especially in the beginning. The commands and concepts like branching, rebasing, and merging can feel confusing until you’ve practiced them a few times. Review collected by and hosted on G2.com.

Git is one of the best and universal ways to maintain a reliable and immutable history of your source code. You can use it on the command line or through various GUI integrations. It is included natively in many IDEs like VSCode. Review collected by and hosted on G2.com.

It lacks robust access controls. You need to configure your own access using ssh, but this is not flexible in terms of granting access to various projects and resources. There is no built-in GUI which makes it difficult to visually view history and track changes. Review collected by and hosted on G2.com.

The best thing about GIT is its speed and overall performance. It also stores repository history efficiently, which makes it easy to keep track of changes over time. Review collected by and hosted on G2.com.

In my personal view, some Git commands often don’t follow a clear logical pattern. For example, "git checkout" is used both to switch branches and to restore files, which can feel confusing. Similarly, "git reset" comes with multiple modes, and that adds to the sense that the command set isn’t always consistent or intuitive. Review collected by and hosted on G2.com.

What I like most about Git is how effectively it tracks changes and manages code versions. In our day-to-day development work, it provides solid version control, making it easy to review what was changed, who made the change, and when it happened. This is especially helpful in a team environment, where clear history and accountability matter.

I also really value Git’s branching feature. It lets us work on new features or bug fixes without impacting the main codebase, and once everything is ready, we can merge the work back in safely. That flexibility helps reduce the risk of accidentally breaking the main application.

Another aspect I appreciate is its integration with platforms like GitHub and GitLab, which makes collaboration smoother. Overall, Git keeps development more organized, secure, and easier to manage—particularly when multiple developers are working on the same project. Review collected by and hosted on G2.com.

One thing I dislike about Git is that it has a bit of a learning curve at the beginning, especially with concepts like rebasing, resolving merge conflicts, and managing branches. For new users, it can feel confusing, and mistakes can happen when commands aren’t used correctly.

Also, when multiple developers are working on the same files, merge conflicts can come up often. Resolving them takes extra time and careful attention, and if they aren’t handled properly, they can affect the code.

Another small issue is that the command-line interface isn’t always very beginner-friendly, and it takes a while to remember all the commands. That said, once you get used to it, Git becomes much easier to work with. Review collected by and hosted on G2.com.

The command-line interface is great and lets us interact directly through the terminal. It’s very fast, and it helps us save, track, and manage code changes. The GitHub integration also enables our whole team to collaborate, maintain a clear code history, and work at the same time on the same codebase, which makes merging during development much easier.

It’s absolutely free and very easy to use, especially with the documentation. It doesn’t need AI to be easy, because it’s already simple and fast to use. AI models already understand Git well, so they can even help keep things organized when needed. Review collected by and hosted on G2.com.

If we’re good at it, then there won’t really be anything to dislike about it. The only downside is that we might get confused while making changes, mess up the branches, and run into merge conflicts. Still, we can always roll back and sort things out. They can't integrate Ai into this , also there is no need for it. Review collected by and hosted on G2.com.

What I like best about Git is its powerful version control capabilities and distributed architecture. It allows developers to track changes in code, collaborate with multiple team members, and maintain a complete history of the project. Features like branching and merging make it easy to work on new features without affecting the main codebase. Git also integrates well with platforms like GitHub and GitLab, making collaboration and code reviews very efficient. Review collected by and hosted on G2.com.

Git can be difficult for beginners due to its many commands and concepts like rebasing and merge conflicts, which require experience to manage effectively. Review collected by and hosted on G2.com.

Every project I start, even the ones that have nothing to do with code, kicks off with a Git repo. It is my safety net. It creates this constant, recurring commitment to the work I'm putting in, and it actually forces me to pause and think about what I’ve really achieved before I move on. It is less about the technical side and more about the peace of mind that comes with knowing every step is tracked. Review collected by and hosted on G2.com.

The commands can be completely unintuitive and It is also way too easy to get stuck in a "detached HEAD" state or mess up a rebase. Review collected by and hosted on G2.com.

Very easy and simple to use, with small and simple commands

We could quickly setup, our local files to cloud

Larger community support and great detailed documentation

Daily tool for collaborative and simple solo projects

great features like branching, cloning, forking

easily integrates with ci/cd pipelines, IDE's Review collected by and hosted on G2.com.

I do like everything about git, but it could be quite overwhelming for beginners due to its moderate to steep learning curve and might get confused by the commands and cli.

Integrating with gui sometimes behave differently than cli Review collected by and hosted on G2.com.

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.