Git Reviews & Product Details

Speed, simplicity, security.

Git is a solid tool, not only for developers, but for versioning everything: photos, text files, code, and so on. Review collected by and hosted on G2.com.

This is a hard question. As git is, for me, the state of the art of the verisioning tool, there is no other tool over it. Maybe the binary handling could be a bit improved. Review collected by and hosted on G2.com.

Everything. From the ease of initializing the files as git, to making commits to managing diffs to pushing on to GitHub. This version control system is just Awesome. I started using version control, about 6 months back, and now I have version control for almost everything I code, from a web app to even websites(Do websites need version control? Its upto you, I do use it with git and push all my commits to GitHub).

Believe me Git and GitHub are the best couple, for best results use them together. Review collected by and hosted on G2.com.

Making lot of branches in Git is easy to do, and very helpful, but I personally face problem a lot of times when I try to merge two branches together, so I think that particular field need some improvement, or maybe its just 6 months, since I have been using the product I need to make my skills better. Review collected by and hosted on G2.com.

At first it felt a little slow and complicated, but after we got used to it, it saved us a lot of headaches and sync issues between developers. What I like best is the way that git updates everything when pulling from my repository. It just feels so easy. Review collected by and hosted on G2.com.

Sometimes simple tasks or simple fixes take too much time to implement, but that's a microscopic problem considering the benefits. Review collected by and hosted on G2.com.

Git is one of the better tool i've ever used.

It simply just works. Review collected by and hosted on G2.com.

All functionalities of git are really very important. I really love it! it is perfect! Review collected by and hosted on G2.com.

The tracking of my code, the log, the branches, the commits ID to move between commits and time travel in my projects. It is the best way to develop with a team and organize your projects. I am a Windows and Linux User and works the same in both operative systems. There are Git good practices for example when you do a commit, you need to know when you're going to write a short message or a long one. Those little details when you are working with Git are very important. With git you're able to work remote from home, that is what I like best. Review collected by and hosted on G2.com.

If you don't know how to handle the conflicts you will have a lot of problems with your teams, it is very important to separate function by module or feature, so every person has different code responsibilities. The leader needs to know how to handle the merge requests. As a leader, you need to know the Stack and have experience with problems so you can fix the conflicts, and as a partner you need to write good commit messages so when your code is about to be merged your leader don't have problems margin. Review collected by and hosted on G2.com.

Local version control. It can save multiple versions of my project so that I can go back if something explodes. Review collected by and hosted on G2.com.

Difficult to get up to speed on how to use and what each command is. Review collected by and hosted on G2.com.

linux based commands, at the very same time would need Gui based tool Review collected by and hosted on G2.com.

Having a windows equivalent would be great where I can do operations through right click , command Review collected by and hosted on G2.com.

In software development, Git is widely used version control system. Using Git, it is easier to manage source code, collaborate. Git is faster and provides data integrity, flexibility. Easy rollback , branch creation and deletion. Merging different branches is smooth. Git is available on various OS. Also, Git provides private and public repos. Review collected by and hosted on G2.com.

Git is command-line based hence, takes time to master it. Merge conflicts are difficult to handle for large projects using only rebase. Reverting to previous commits can be tricky. Too many commands to do same or similar tasks. So, need to be well aware of each. Review collected by and hosted on G2.com.

The crowd praises the beauty of Git internals, but it is not improving overall user experience, not at all; worse — horns and tails of mentioned internals actually stick from most unexpected places introducing complexity that could easily be avoided. Review collected by and hosted on G2.com.

Poor design decisions led to leaking abstractions:

* Design decision: "do not record changes, just store snapshots of working copy". Following that leaves no way but to detect file copying/renaming (using their contents' hashes). It is fine until user doesn't copy/rename _and_ change file between snapshots (refactoring, atomic commits — that sort of thing). Which leaves no way to Git but to *guess* what was renamed/copied to where, which (guessing) is so easy to trick.

* Design decision: "only referenced version graph heads are meaningful". Following it introduces so-called "detached HEAD" state and situations like "I've contributed changes on top of a tag and now they are gone". Review collected by and hosted on G2.com.

Git is very flexible and can be adapted to a lot of different kinds of workflows. There are several tools and services that compliment it but probably github takes the first price as it's by far the best online hosted git repository service. The way git handles branching, rebasing and remote repositories is very solid and gets the job done efficiently. Sharing code with others through a central server is easy (by using branches) and working on several features at the same time is a piece of cake. Review collected by and hosted on G2.com.

The command line could take a while to master and it's not for beginners. The concepts used are not very intuitive initially and it takes some effort to grasp them. Compared to mercurial, there's no feature that can match the ease of use of mercurial queues. There's also a lack of easy exporting revisions, change sets and other information to multiple formats, it's doable but not simple. I have to keep lots of aliases for common operations that should be a simple command but in practice they are multiple. Also I have to use several tools along side git for lots of tasks. Review collected by and hosted on G2.com.