Want to see who topped the 2019 Best Software Awards?

Git

4.7
(198 reviews)

Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.

Work for Git?

Learning about Git?

We can help you find the solution that fits you best.

Git Reviews

Chat with a G2 Advisor
Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • Industry
Ratings
Company Size
User Role
Industry
Showing 200 Git reviews
LinkedIn Connections
Git review by Milagros Nazaret L.
Milagros Nazaret L.
Validated Reviewer
Verified Current User
Review Source

"The ideal version management system for projects"

What do you like best?

Git is a software designed by Luis Torvalds, open source that allows us to have mirror versions of our projects and thus simplify the way to correct errors and effectively maintain a project in an orderly distributed and robust.

it has great features such as focusing on collaborative work, that is, several people can modify, create or eliminate part of the project and versions of it in a structured and orderly manner, allowing generating workflows that facilitate the development of large projects. In comparison with other systems, the storage of information does not line with the objective of maintaining the image of all the files, all through ramifications of the project, another of its advantages is that most of the operations are carried out locally, which leads to another of the great advantages GIT only increases the changes to the files or directories that are modified, created or deleted, that is to say that it considerably reduces the time it takes to show the changes made especially if it's in the application in production, it should be noted that using this software it is impossible to make changes in the content of a project without being approved. Git also allows you to return to previous versions quickly and easily, return the project or files to the version you decide to return without taking into account any of the changes that were made after that version. Git provides many tools that facilitate the work. As for security, it makes use of SHA1 tree systems, ensuring that until the verification of the number or signature is not made, no changes will be made.

What do you dislike?

Git requires time to learn because it has many new concepts and orders.

Training should be given for the proper use and management of the tools to the users to avoid that errors are commented although they can later be undone. As for the parameters, sometimes they are very long. It's important to know the command line what is difficult at the beginning to all those who are accustomed to the use of the graphical interface

Recommendations to others considering the product

Probably you have a bit of difficulty at first to use the Git version control system especially if you aren't used to using the command line but it will be worth it especially when you need to return to an earlier stage of the project. Git will allow you to organize the code, generate readable code, work as a team among other things.

What business problems are you solving with the product? What benefits have you realized?

Every developer knows that it's essential to have support of their projects at various points of their development, GIT was designed in a distributed manner which allows each developer to have full local control of the project, as well as having restoration points in case the latest changes aren't correct or the project should be modified from a specific point, git allows you to return easily through little commands, if you want to modify a project just clone it and locally make all the changes and tests you want. You can also observe all the changes you have made in your project throughout the development.

Sign in to G2 Crowd to see what your connections have to say about Git
Git review by Dylan C.
Dylan C.
Validated Reviewer
Verified Current User
Review Source

"Easy version control "

What do you like best?

How adaptable it is to any situation. It is essentially an all-inclusive package for everything you need when writing and commiting code as a team member. It's features are fairly simple to learn and crucial for maintaining any sort of version control in your applications.

What do you dislike?

Not a fan of how not user-friendly it is. it is very complicated to learn all the ins and outs of the API, and even then it is hard to remember all the small details you need to be able to commit your code effectively. It takes many people months to learn how to do it properly, and even then they often do it wrong until corrected by someone who knows what they're doing. it would be amazing if they had a quality how-to video that went into all the small details of each command in an easy-to-remember fashion.

Recommendations to others considering the product

Learn it early and learn it well. It is worth every minute.

What business problems are you solving with the product? What benefits have you realized?

Solving version control issues. It is really good for testing out new features and branching different versions without having to manually separate the folders in your file system. This allows multiple team members to work on the same code at once without changing the underlying backend files. It also is very good if you need to rollback to a previous version because of bugs/issues/performance/etc. Having git means you can rollback incredible easily and also see where the problematic changes occurred.

What Version Control Systems solution do you use?

Thanks for letting us know!
Git review by Jose Rafael C.
Jose Rafael C.
Validated Reviewer
Verified Current User
Review Source

"My git review"

What do you like best?

Every software developer should use git. This is the best way to track changes to a code. It is also very useful to see the changes that are made in the code.

What do you dislike?

At first and as all its use can be confusing. Learning how to use it can be frustrating and especially when several programmers who are participating in the project do not know how to use it correctly. There is a lot of confusion when the project is starting and the changes are constant.

Recommendations to others considering the product

Git should display error messages in more detail. He should even give advice on how to solve them. Also give an alert or warning before the code is damaged by a bad command.

What business problems are you solving with the product? What benefits have you realized?

We as a company that develops software, we give the client the entire git repository and in this way see the changes made over time. This gives the customer more confidence. Another point in your favor is that there can be two codes circulating since it is extracted from git.

Git review by Shahram J.
Shahram J.
Validated Reviewer
Verified Current User
Review Source

"The defacto Version Control System"

What do you like best?

A capable tool with profound insight into the concept of version control. A diverse set of command-line tools.

I also like history rewriting and multiple origin feature. You can point your local copy to the local repository of a colleague rather than that of the server.

What do you dislike?

Sometimes command line parameters are so lengthy that it is not easy to keep them easily in mind.

Inconsistent behavior among versions. e.g. core.fileMode=true configuration flag causes git to consider many untouched files eligible for inclusion in the commit.

There is no way to avoid downloading the entire commit history of a repository into the local copy. This harms performance of cloning when working with many submodules.

Recommendations to others considering the product

You may be disappointed at first attempts, because you may have different image of how a version control should work. But in the course of time you will realize that git has a different and more practical approach to the concept of version control.

What business problems are you solving with the product? What benefits have you realized?

distributed version controlling among all the company locations over the world

Git review by Alejandro E.
Alejandro E.
Validated Reviewer
Verified Current User
Review Source

"My favorite version control system"

What do you like best?

It is fast to place changes in stage and commit them. Also the basic us of the application is very easy to use, even if you don't use the user interface.

What do you dislike?

It is difficult for me to perform advanced tasks. Merge changes and fix conflicts must be done manually and the side by side comparison is not clear enough.

Recommendations to others considering the product

Before us it is a good idea to take the basic training in order to understand the basic of the VCS. I think is the best option for track the changes in the text files like source code.

Generate branches could be very useful but merge them could be difficult, some times it must done by hand.

What business problems are you solving with the product? What benefits have you realized?

The tracking to the changes in the source code was a common problem in my team, the projects we work on are very large and also the developers works in more than one project at the same time. The use of version control system allows to everyone in my team to track their own changes and make the releases easier.

Git review by Janaka B.
Janaka B.
Validated Reviewer
Verified Current User
Review Source

"Powerful version control"

What do you like best?

Git is one of the most flexible, powerful version control systems I have worked with.

Nevertheless, it is also super easy for a beginner to get started with!

Combined with GitHub, Git is the unmistakable winner on sharing, collaboration and open-sourcing.

What do you dislike?

Advanced configurations (e.g. managing multiple branches) can sometimes be overwhelming for inexperienced users

Recommendations to others considering the product

If your users are on multiple platforms (e.g. Windows and Linux/Mac), configure offending parameters (line breaks, file permission tracking etc) in a way compliant with all platforms

Get used to common tricks like setting up SSH for passwordless pull/push and using --depth when cloning large repos

What business problems are you solving with the product? What benefits have you realized?

Maintaining source code of certain internal and client projects

Exposing samples and other source material as reusable code bases

Accessing latest codebases for multiple open-source projects related to our products

Git review by Matthew P.
Matthew P.
Validated Reviewer
Review Source

"Git for Collaboration"

What do you like best?

Each time a team member makes a change to the code Git shows the exact changes. Git is overall a great log/tool to track the changes during the course of a project that requires collaboration. Not to mention it is easy to use.

What do you dislike?

To push your files to Git you have to enter several command lines in power shell. This can be tedious at times. Especially when you are tracking multiple changes to a project in a short period of time

Recommendations to others considering the product

There is a little bit of a learning curve when first starting to use it, but it is well worth it

What business problems are you solving with the product? What benefits have you realized?

There are three problems we are solving with Git. 1) We are collaborating on a SQL project. This tool has been excellent in tracking the contributions of our team members and noting what changes have been made to our files. 2) If there is ever an issue with our code we can use Git to role back to a previous version. This is crucial as our work is for an external facing product 3) If we need to access a file and one of our team members is unavailable we can always refer to Git

Git review by Tushar B.
Tushar B.
Validated Reviewer
Verified Current User
Review Source

"Excellent version control system"

What do you like best?

Every company should use this. It is by far the best version control system. Very maintainable and robust. Command line utility is just super amazing. Squash commits is the best feature. Also, rebase is something very interesting. I can go on and on this is the best version control ever.

What do you dislike?

Nothing. Everything is perfect. Just one small thing is that the command line utility is stronger (UI for this could be made better and easy to use).

Recommendations to others considering the product

It is by far the best version control which is easy to use with good quality support and excellent features. Please try this out before using any of the other ones out there.

What business problems are you solving with the product? What benefits have you realized?

Using git for version control and command line to push code changes, rebase, merge, stash, squash, etc.

Git review by Fernando Q.
Fernando Q.
Validated Reviewer
Review Source

"Git is basic in programming"

What do you like best?

What I like the most about Git is the possibility of keep track of the changes thst are being made in the code, and also being able to easily get back to a earlier commit.

What do you dislike?

What I dislike about git is that commits are no very easily to manage unless you have a compatible ui tool.

Recommendations to others considering the product

Git is a very powerfull tool for tracking ypur code but I stringly recommend to check plugins and ui tools compatible with Git and the other applications that you are using every day, be sure there is a Git plugin to make your life easier

What business problems are you solving with the product? What benefits have you realized?

The main problem that git is resolving to me is dealing with doubtful clients that ask for changes on theirs web, then they didn't like them and want you to get back to what they had before. With Git this is si much easir to manage.

Git review by Siddharth W.
Siddharth W.
Validated Reviewer
Review Source

"Does abny other Version Control System exists?"

What do you like best?

Merging Branches made so easy

Learning and using git is easy as there is a lot of community support available

The code can be reviewed before merging into the default branch

Backup system is awesome

What do you dislike?

Spelling a wrong command might lead to an unwanted code to be changed, therefore, you have to be very careful

Lack of plugin support for major IDEs

Recommendations to others considering the product

It is great tool to keep track of all the projects and create different environments of various purposes. This allows you to see hhow the code behaves before being merged into the main branch and you could make necessary changes, if required. It is a great tool for the developers to keep track of all the chanfges made to the code and the defects they fix, or need to fix

What business problems are you solving with the product? What benefits have you realized?

We are using Git for maintaining the development code for the clients. The devs push their codes into the Git, it is then reviewed and tested, if all is good, then the code is merged into the Main branch. So now we know that our code is safe and backeup

Git review by Marc V.
Marc V.
Validated Reviewer
Review Source

"Version control for all your needs"

What do you like best?

The best features of GIT are:

- It is free and open source.

- It handles from the most small personal pet project to a very large project.

It is easy to learn the common use (clone, add, commit, pull & push) but at the same time have all advanced features that you can need in a future (merge, cherry pick, diffs ...)

It is faster than other version control solutions that I used. I suppose that this is why it performs nearly all operations locally, giving it a huge speed advantage on centralised systems that constantly have to communicate with a server somewhere. You can see the comparatives in this link https://git-scm.com/about/small-and-fast

The have a big community and you can find always the solution for your problem.

It is distributed, that does mean that allow your team to work separately and disconnected.

What do you dislike?

I think is the best version control tool, and if I to say something that I dislike perhaps is the understand the concepts of local copy, stash, loca repository and remote repository.

Recommendations to others considering the product

Try it, and also try to understand what is different from the others version control systems.

What business problems are you solving with the product? What benefits have you realized?

The version control of my personal projects and also the professionals.

Git review by Jason D.
Jason D.
Validated Reviewer
Verified Current User
Review Source

"Git - Free, secure, concise, version control for all"

What do you like best?

I like that with Git using the command line interface I have full control over all my interactions with the Version Control system. A recent addition in support of Git is it's integration into Microsoft's Visual Studio, Microsoft's Team Foundation Server and Microsoft's Visual Studio Code.

What do you dislike?

Though the command line interface is powerful it is also daunting for those of us that are used to GUI. fortunately the git --help command is very helpful and points discerning developers in the right direction.

Recommendations to others considering the product

Harness the power of the command line but tread lightly

What business problems are you solving with the product? What benefits have you realized?

At Kizan we use Git to help us manage the version control of source code for many large custom software development projects. It gives us one less thing to have to worry about. Git takes care of it all. Git is also cross platform so it doesn't matter if teammates are using Windows PCs or Mac Books.

Git review by Rick K.
Rick K.
Validated Reviewer
Verified Current User
Review Source

"Git for version control"

What do you like best?

Git is very widespread. I think nearly every developer has some experience with it, so it makes a good medium for exchange of and collaboration on code. Its popularity also makes for the availability of a lot of documentation and help. And it does the job for which it is intended.

What do you dislike?

My biggest complaint, in my own opinion only, is that resolving merge conflicts is harder than it should be. Also there seems to be more "religious wars" than there should be about how to accomplish some fairly common tasks. Lastly, at least in my own experience, discoverability (search) stinks.

Recommendations to others considering the product

Can't go too far wrong with Git, unless you really need to squeeze the last ounce of goodness from your version control system, in which case you'll want to investigate whether some of the more modern alternatives fit your needs better.

What business problems are you solving with the product? What benefits have you realized?

Git, along with some continuous deployment tools, gives us a single source of truth for our software; a focal point for discussion; a process by which experienced developers can help those with less experience in a particular area. Its popularity makes it easy to bring new people on board. The Gitflow workflow that we use helps us manage our development efforts and keep straight our various software versions.

Git review by Martín Pablo C.
Martín Pablo C.
Validated Reviewer
Verified Current User
Review Source

"Best cvs"

What do you like best?

It is very fast to use, branching is very simple once you understand how it works. It is a tool that you must use it. There are several git servers in the market and some of them allow you to create private repositories for free.

What do you dislike?

Several times I need to Google some commands because I don't remember them but I think that is the price for having such a powerful tool.

Recommendations to others considering the product

Is the de-facto csv

What business problems are you solving with the product? What benefits have you realized?

More control on the code is uploaded to the server. You can divide the work on different branches depending on different priorities. You can create experimental features. You can revert the changes when something was wrong. You can blame people for their mistakes

Git review by Peter P.
Peter P.
Validated Reviewer
Verified Current User
Review Source

"Git is incredible for keeping track of source code changes"

What do you like best?

I like Git because repos are stored in their entirety both locally and in remote repos. It's easy to work with from the command line, it integrates well with popular editors like sublime, atom. There are some great bash scripts to help you know where in a repo you are and what's been changed on github

What do you dislike?

There's not much I dislike if anything i'd say looking a diffs in a terminal but that's something ill need to brush up on it's not really a dislike i guess.

Recommendations to others considering the product

For anyone who hasn't used git and is new I would recommend Googling git interactive tutorial there are online tutorials where you can practice using git right in your browser after that I'd say setup a repo in bitbucket or github and start testing out git

What business problems are you solving with the product? What benefits have you realized?

Working with teams all over the world and contributing to different projects. I've also been able to help co workers learn the basics so they can work on projects

Git review by Christian C.
Christian C.
Validated Reviewer
Verified Current User
Review Source

"Easy to learn but difficult to master"

What do you like best?

Git is very popular, so the community surrounding it is plentiful, which translates to being easy to find tutorials and QAs regarding most of the issues you might find by using it.

For plain text files, it's extremely useful and optimal in terms of performance.

What do you dislike?

For starters, the documentation needs improvement.

Native merge conflict display can also be a pain to handle, so the use of third-party is highly recommended.

Furthermore, it's not suitable for large binary files, which is something valuable in game development.

What business problems are you solving with the product? What benefits have you realized?

Git serves as my preferred SVS for my indie game projects, as it's been easier to learn than other systems such as Mercurial and SVN.

Git review by Carey D.
Carey D.
Validated Reviewer
Verified Current User
Review Source

"Awesomeness"

What do you like best?

I like GIT specially using it in terms of development, I often use the command line interface in Linux and Windows. the program is very portable and cross compatible with different operating system and servers.

I use GitEye and TortoiseGit when I want to see the commit history, the branches and tagging visually. It improves my code organization and best when am refactoring code.

What do you dislike?

Support for GUI, i hardly find a good GUI that could be used in GIT

Recommendations to others considering the product

Git is highly recommended as a version control tool for developers.

What business problems are you solving with the product? What benefits have you realized?

Version Control is very crucial in terms of developing large code base programs, specially apps or programs written in C/C++ in which are very messy.

I've written code and used the version control features of GIT on languages like PHP, Node.js, C/C++ and HTML.

Git review by Eric M.
Eric M.
Validated Reviewer
Review Source

"Reliable, distributed version control for everyone"

What do you like best?

Since Git is a _distributed_ version control system, every copy of the repository works as a standalone repository (there is no "one true master" copy of the code). This makes scaling projects easy and means everyone working on the code has, in a way, backed up the codebase for the team!

What do you dislike?

Working with the Git CLI can be a bit cumbersome. The GUI tools available don't make it an easy system to learn, either. The learning curve for Git users is super steep.

Recommendations to others considering the product

Git is heavily biased towards command line users or those who are incredibly comfortable working with minimal instruction or support. Introducing it to your development team will require at least someone on hand to answer questions and lend support when other engineers get stuck.

What business problems are you solving with the product? What benefits have you realized?

We house all of our code in Git repositories, many hosted online via services like GitHub and BitBucket. We also use Git to collaborate directly with one another in a team setting, making code sharing incredibly fast and not reliant on the stability of an online vendor.

Git review by Trevor H.
Trevor H.
Validated Reviewer
Review Source

"Git. A kernel developer over-engineered something simple, but its all we got."

What do you like best?

git can do anything. Which is a good thing, but truth be told, most people just need a simple workflow. I guess the best thing about git is its everywhere. Everyone knows it. You don't need to teach anyone who joins the company how to use it. (Maybe help out here and there when they have a confusing merge or cherry pick or rebase or something), but in general, every developer worth a grain of salt knows git at a basic level. What's good is that its fast, efficient, and cross-platform. There many tools built on top of git too.

What do you dislike?

You know the unix philosophy? Every tool should do 1 thing. Git has a different philosophy. "Lets see how many program flags we can give a single binary." Its just too confusing for beginners. Some people have learned the intricate ins and outs over time, and I pity them, because who cares... all anyone ever wants is too pull, push, edit, merge. Yet git so many quirks that everybody ends up wasting time googling super simple things just so they can go to the first stackoverflow question upvoted by 10 million people so they can copy and paste the obscure poorly named flag. Simply put, git is a tool only an engineer could love. But maybe I'm not a true engineer, because I just want to get things done.

Recommendations to others considering the product

Don't try to learn it all. It's a waste of your time. There is so much more interesting things to spend time learning, and becoming a git guru is not one of them. I recommend you just work on a project and use git based on what you need to do. Eventually you can create shell aliases and just use those. Then you stop thinking about git and just do what you need to for your workflow.

What business problems are you solving with the product? What benefits have you realized?

Like I said, git is like air. You just don't program without it in 2017.

Compiler - check

Editor - check

Git - check.

Its essential to any project for maintaining history in a distributed way. If I joined a company that was emailing around code, I would probably send a resignation in immediately. Or demand immediately change. The biggest day-today benefit for me, is it lets me code anywhere. Everything is distributed, so I program at work, at home, on my laptop under the stars. My code is backed up and accessible anywhere I can find a keyboard. That's reassuring, and very important from a business perspective. Oh, and of course, you'll never lose history. (Unless you force push, but most companies will put a blocker in place so no one accidentally does that)

Git review by User
User
Validated Reviewer
Review Source

"Perfect tool for source control."

What do you like best?

The tool allows to maintain a proper history of source code and helps in version control of the projects. Keeps a log of previous versions and helps revert to any stable version in case the ongoing development breaks the stable one. Helps team collaborate with the help of various UIs for git like GitHub, Gitlab, Bitbucket etc. Allows creation of branches and creation of pull requests for team members to review before merging code into the main development branch.

What do you dislike?

rolling back to the previous commit is a bit complicated for beginners as it is a bit too risky and can lead to major losses in the work.

Recommendations to others considering the product

Git is a really great tool and one should definitely consider exploiting its services and usages to the full. It really helps understand the work environment in teams and how should one maintain their work in conjunction with others. Also, it prevents you from losing your work in case any mishap happens or you accidentally override the functional code.

What business problems are you solving with the product? What benefits have you realized?

Git is being used for collaboration of teams of developers testers as well as other entities so as to contribute towards various products and deliver a fully stable end product.

Git has seamlessly allowed maintenance of the functional products and thus contributed towards maintaining the software development lifecycle stages.

Git review by Leif K.
Leif K.
Validated Reviewer
Verified Current User
Review Source

"Git good for source control, especially decentralization"

What do you like best?

Git allows you to have a local copy of the source code, you avoid the locking problems that CM programs like ClearCase have, and it's generally not that hard to use. I mostly use Subversion at work, which is great and has most of the advantages that Git has. Subversion is easier to use and setup than Git, but the whole decentralized repository aspect of Git allows you to commit changes locally when not connected to the server with your repository, which is nice if you aren't connected to the internet all the time. Git is also hugely popular lately, so you'll have tons of support for any questions you have.

What do you dislike?

The learning curve on Git is steeper than Subversion. It's not as intuitive and you need to spend some time learning how to use it properly.

Recommendations to others considering the product

Take a look at Subversion as well, both Git and Subversion are similar and are good options for CM tools.

What business problems are you solving with the product? What benefits have you realized?

Git is a configuration management (CM) tool used to provide source control for software. If you are writing software for anything other than playing around at home, you absolutely need to have CM control. The benefits include being able to look through the history of updates made to the code by you or anyone else contributing to it, being able to create a specific release version of software and recreate the source, and the ability to check what you've changed before updating the source code.

Git review by Adrian King L.
Adrian King L.
Validated Reviewer
Review Source

"Intense!"

What do you like best?

As you can see from my reviews, I like simple things because I want to get things done immediately and git helps me with that; but don't be caught by the simple command-line tool, this little guy is fully featured for your version control needs but it is also amazing in such a way that you can start controlling your source in just a few add, commit and push

What do you dislike?

It requires you to read through a lot of documents in order for your to fully utilize the potential of git, though it is just a preference between software developers because sometimes; you don't need that much to do a lot.

Recommendations to others considering the product

The learning curve for the full feature of git is quite hard to master but you don't need that much in order to achieve your goal with git

What business problems are you solving with the product? What benefits have you realized?

We were able to revert our code to a previous version when something arises, we are able to know what kind of changes have messed up our system hence we can work on it again from a different approach, it allows us to store also documentation like how we would store code which is a amazing because we can now keep track of features together with commits

Git review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Git is one of the most popular SCM solution available today!"

What do you like best?

Git is one of the most widely used and popular Version Control System. Though it is provided as a free software, it is still one of the most popular ones and arguably one of the best. Older Centralized SCM systems had many disadvantages and Git's distributed Architecture makes it highly advantageous.

What do you dislike?

There's not much to dislike about Git but the availability of Advanced Options makes it a complex tool if you want to go deeper. The resolution of Merge Conflicts is one of the most tedious tasks in Git and there need to be made some innovative changes that make Merges easier for non-advanced users.

What business problems are you solving with the product? What benefits have you realized?

We are using it as our primary SCM and VCS tool and have no plans to change to another tool in the near future.

Git review by Kayla B.
Kayla B.
Validated Reviewer
Verified Current User
Review Source

"Get git!"

What do you like best?

It's widely considered the standard for source control these days, so a number of handy gui tools to help visualize your git usage exist (e.g. GitKraken, SourceTree), making it easy to teach beginners about proper version control processes during the development life cycle. On the same token, more experienced users can easily access it from the command line making it faster and more efficient if so desired. It also has great free remote storage options that support it (e.g. Github and BitBucket).

What do you dislike?

When not integrated with a gui tool, more complicated actions like settling merge conflicts that occur from re-basing (among other things) can be difficult to visualize and correctly fix.

Recommendations to others considering the product

If you've never used it before, get a GUI tool that integrates with Git to get a better grasp on what is occurring when you perform certain actions.

What business problems are you solving with the product? What benefits have you realized?

Version control is necessary for the success of any development team. Inevitably someone will over write another person's changes, or someone will push broken code to production and a roll back will be needed, or a bug fix will come up that's completely unrelated to the current project and somehow needs to get into production and included with the current changes so you don't risk the new project deployment overriding the fix once it's ready to be deployed. Version control solves all of these problems. It gives developers the ability to go "okay, this broke, what changed?". Without version control you don't know what changed or who changed it without having a number of backups and spending an exuberant amount of time tediously going through work line by line with a fine tooth comb to discover this information. Git helps you solve these issues 100x faster without a migraine.

Git review by Matthew G.
Matthew G.
Validated Reviewer
Verified Current User
Review Source

"Git is downright awesome."

What do you like best?

I really love Git's distributed model (I have a copy of the repo, github has a copy of the repo -- my collaborators have a copy). It makes working with the code really easy. I love how git allows me to clean up my history before I push it to a remote repository. I love how I can visualize changes with third-party tools (e.g. git-x) before pushing and how I can understand the evolution of the code more cleanly.

What do you dislike?

Git has a steep learning curve. If you're not up for putting in a little time to learn the different workflows that work well with git, then you're probably in for a lot of pain.

What business problems are you solving with the product? What benefits have you realized?

We write code. Having a version control system is critical and git allows me to work with the code in ways that other VCSs lack. Pair that with the abundance of third party tools (e.g. git-x, github) for working with `git` and it makes things like code-reviews so much easier than if I had to send patches around or if we were all working with a central repo.

Git review by Jake S.
Jake S.
Validated Reviewer
Verified Current User
Review Source

"Best version control software out there"

What do you like best?

Simple, easy, and fast. Tons of documentation and tutorials out there so it's easy to ramp up your team on how to use it. Plenty of UIs built on top of it too. Git is the dominant version control system at many companies so it is a valuable skill to have on your resume as well.

What do you dislike?

Disadvantages of Git are:

- A steep learning curve (although there are lots of resources for learning and making it easier to use)

- It can become slow when handling binary files - it's not the ideal software for collaborating on e.g. a Word document.

Recommendations to others considering the product

Git is the best version control system I have used. It integrates nicely with IDEs and other development tools. It has an enormous community providing support and software for it. It goes hand in hand with Github, the most common way for sharing open source code on the Internet.

What business problems are you solving with the product? What benefits have you realized?

I've used Git for version control at many companies in the past. It makes collaborating on software easy. It allows thousands of engineers to contribute to the same codebase without overwriting one another's changes.

Git review by Abhishek S.
Abhishek S.
Validated Reviewer
Verified Current User
Review Source

"While I haven't used other SCMs my experience with git has always been AWESOME!"

What do you like best?

The best thing about git is its ease to use. Sure there can be tricky things(merge conflicts etc) sometimes but git can be used by both beginners and experts alike because of its ease to use.

What do you dislike?

Probably that sometimes there can be way too many concepts to learn if you dig deeper. But I guess that comes with a tool with advanced features as well.

Recommendations to others considering the product

If you are a a beginner stick to basics.

If you are an expert use git with supported technologies like Atom, oh-my-zsh etc, intellij and your experience is bound to be wonderful when using this software

What business problems are you solving with the product? What benefits have you realized?

Can't disclose much because of agreements but you can say mostly e-commerce. The benefits are realized best when combined with a review tool. It makes code development and review so easy if used correctly.

Git review by Sabbir M.
Sabbir M.
Validated Reviewer
Review Source

"Project collaboration - made easy by Git"

What do you like best?

The best thing to like about git is the ease of collaboration among team members. Team members can work on their own, keep committing in their own branches without the fear of conflict. Merging can be done only at the end when all the members are done. So team members can keep working independently. Besides version history is another great feature. At any time, you can go back to see how your code looked like in past.

What do you dislike?

Conflict resolution process is not friendly. Sometimes, it really takes some real good deal of time to fix the conflict.

Recommendations to others considering the product

Git is definitely a better choice for version control of your source code. It maintains your history of source code in branches, therefore, it is very much easy to look back into your code history. The branches keeps your code version organized. In addition to keeping your code history organized, the branches also makes it easier for the collaboration of your project among all your team members. Each of the team members can independently work on their own branch and merge only at the end.

What business problems are you solving with the product? What benefits have you realized?

We are using git for the development of the core product of our company. We create new branch for each of new feature required. All the code changes are made to the same branch. Quality assurance testing is done in the same branch. Finally when everything is verified, the branch is merged to the master branch.

Git review by User in Higher Education
User in Higher Education
Validated Reviewer
Verified Current User
Review Source

"Review of Git"

What do you like best?

Git itself is a great way to implement version control for your code. It is widely adopted and so there are plenty of resources available to learn how to use Git. It can be confusing at first, but after understanding some of the reasoning behind the command syntax, it is well worth the trouble to use Git with your projects.

What do you dislike?

The Git Bash and Shell that are installed with Git are terrible. They are not intuitive at all and can significantly increase the amount of time and effort it takes to get something done with Git. However, being so widely used, this can be countered by using a variety of software with Git integrations. Text editors (Sublime Text), shell emulators (ConEmu), and remote repositories (GitHub, GitLab, BitBucket, etc.) are all available to replace the atrocious nature of Git Bash and Shell.

Recommendations to others considering the product

Take some time to get to know the nuances of Git. Having a thorough understanding of the reasoning behind many decisions in Git will simplify the workflow that you follow. In addition, identifying good resources to couple with Git in place of the Bash and Shell installed with Git will significantly improve productivity. Overall, Git is a good thing to know as it is widely used in the industry and for personal or open source projects.

What business problems are you solving with the product? What benefits have you realized?

Git is all about version control and code management. And it does a great job. You are able to track your changes easily while still being able to revert changes that may have caused issues. Branching provides a great opportunity for separation of work and coordination within a team.

Git review by Johan - Manos H.
Johan - Manos H.
Validated Reviewer
Review Source

"Great tool - poor UX"

What do you like best?

The biggest advantage of git compared with similar tools is its distributed nature. Being distributed means that you can use it without needing a serve running and thus becomes an excellent candidate when starting your own project at home and scales very nicely as well later on when you wish to have more collaborators. Other advantages is its power. With git you can do pretty much everything ("edit history") but unfortunately the usage of the tool from the cli starts becoming less friendly.

What do you dislike?

Usability. The more power, the harder it is to provide a friendly interface. Git from the command has a steep learning curve if you want to do something out of branching, commiting and merging. Even those can be somewhat confusing since you can do the same thing in different ways. There are some external tools like git-flow that alleviate this issue but I think that git could still be more user friendly.

Recommendations to others considering the product

Great free tool that pretty much everyone uses. Scales great from a personal project to a huge one with many developers. A lot of power and customization as well!

What business problems are you solving with the product? What benefits have you realized?

Revisioning development of software and web for both personal projects and daytime work.

Git review by Joe B.
Joe B.
Validated Reviewer
Review Source

"Git. Powerful but Arcane."

What do you like best?

Once you've got a godly understanding of how git actually works, you can manipulate your commit history to be exactly how you want it. It's completely decentralized so you don't need to lock files, or sync to a server if you don't want to. It's light weight (branches are just labels pointing to commits) and you can init a repo where ever you want. The ability to add hooks add another level of power to having your repository.

Also, it's free.

What do you dislike?

The learning curve was large. Having someone explain how git works really makes the experience much better.

Recommendations to others considering the product

Learn the more advanced features of git, like patchmode add or interactive rebase.

What business problems are you solving with the product? What benefits have you realized?

Source code repository. Version history.

Git is really fast. Branching is super quick. Having a commit history rather than a file revision history makes sending commits and integrating pull requests very easy.

I also use git in random places. Because of it's small footprint if I'm messing with a ton of config files on a system, i might init a repo in a folder, add everything, and then start changing the files. I can keep a version history and it's all self contained within the .git folder.

Git review by Rodrigo T.
Rodrigo T.
Validated Reviewer
Verified Current User
Review Source

"essential tool for project collaboration"

What do you like best?

it's simple and productive. A thing I really like about Git is that it's very intuitive and has a good documentation, so you can get into solutions fast. It's an essential tool for project collaboration and code versioning.

What do you dislike?

git desktop apps. It crashes a lot and is not that intuitive. But maybe because I usually prefer to use command-line tools

Recommendations to others considering the product

you can also use in conjunction with GitHub and extensions such as hub

What business problems are you solving with the product? What benefits have you realized?

I'm using it to control versions of several private and opensource softwares. It's simples to keep projects working with lots of engineering concurrently coding on it.

Git review by User
User
Validated Reviewer
Review Source

"Unparalleled Source Control"

What do you like best?

Git is a feature-rich, dependable, flexible and all-encompassing versioning software. With sufficient experience, one can use Git to become excellent at efficiently developing code, maintaining it, and correcting mistakes as needed.

What do you dislike?

Git can be quite hard to learn at first. Until you are very proficient, mistakes with Git can be VERY stressful. What adds to the complexity is the fact that there are many ways to achieve the same outcome. To know the actual difference of those routes, you have to have deep knowledge about how Git works underneath.

Recommendations to others considering the product

Take the time to learn Git on the front-end and save yourself a lot of stressful situations. Be slow with your actions unless you are proficient. Get personal with the way you use Git, develop your own sequences of commands and you will learn as you go.

What business problems are you solving with the product? What benefits have you realized?

Source code history and versioning.

Git review by Sara Z.
Sara Z.
Validated Reviewer
Verified Current User
Review Source

"Really good software of versioning and revision control distributed"

What do you like best?

I like all of this tool. The way of working is really helpful; it allows you to have on your local machine the entire repository what it means that if there is a problem on the remote repository we can able to recover most of the information because it will be on our machine. Another advantage of having the whole repository on our machine is that we can have as many branches as we want in local, and then, choose when we want to push them. Also, it has many options to manage the content in the repository and it offers a good online guide with information about all commands, options... The tool that shows you the state of the branches is intuitive, the same happens with the tool that allows you to check the changes that you had done...

What do you dislike?

In fact, I do not dislike anything of Git. Maybe I can say that it is a bit difficult to understand at the first time, especially if before you have worked with another versioning and revision control tool. However when you get the Git's methodology all these problems disappear.

Recommendations to others considering the product

From my point of view is the strongest software of versioning and revision control distributed that we can use nowadays.

What business problems are you solving with the product? What benefits have you realized?

Obviously, the problem that Git solves is the need to have a software of versioning and revision control distributed and with this tool it could be possible.

Git review by Daniel M.
Daniel M.
Validated Reviewer
Verified Current User
Review Source

"Command line power"

What do you like best?

It is source control with a lot under the hood. I am also a big fan of the bash command line that comes packaged with it.

What do you dislike?

The complexity, trying to merge your branch or any code for that matter for the first couple times is very intimidating. Because it is all via the command line primarily it can be hard for new users to adopt without taking some kind of class.

What business problems are you solving with the product? What benefits have you realized?

Managing differences in code. The ability to go back and look at the changes that you made a few years is invaluable. Because Git has such a large user base, it has a plethora of support around it and is going to be supported for a very long time.

Git review by Alan D.
Alan D.
Validated Reviewer
Review Source

"This is an awesome tool for source control with tons of power"

What do you like best?

The fact that you can do everything from the command line if you'd like.

That it is universally integrated into just about every IDE if you would like to do it that way.

The fact that you can usually find out how to do anything with a Google search.

What do you dislike?

Sometimes there is more than one way to do things and that can be a little confusing.

Recommendations to others considering the product

Learn the command line, it will make your life a lot easier!

What business problems are you solving with the product? What benefits have you realized?

It makes Agile development with multiple developers working on multiple features very easy because we can branch and merge with ease. Also pull requests give us built in code review which is awesome.

Git review by Akim D.
Akim D.
Validated Reviewer
Review Source

"Needed for all developers"

What do you like best?

Git is used everywhere, so learning it is largely worth it let alone for this sole reason. Fortunately, it's also a powerful and versatile tool. It is regularly updated with new nice features.

The ecosystem is amazing (GUI, web sites, Stackoverflow answers, integration in IDEs).

What do you dislike?

The initial learning curve is quite steep, but there's a host of online documentation to help the novice.

And many tools (text editors for instance) hide part of the complexity (e.g., Emacs, VS Code).

Recommendations to others considering the product

Make the transition! It is no so hard, and totally worth it.

What business problems are you solving with the product? What benefits have you realized?

I'm saving my own data with Git, just in case my machine has a problem.

I'm sharing work with all my colleagues.

I'm contributing to other pieces of software, especially Free Software.

Git review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"It's my go to for version control."

What do you like best?

I like that it most of the time knows how to merge intelligently when both the upstream and my copy of a file have been modified. There is still some times when you need to perform merges by hand, when the conflict is just can't be done automatically. I like the ability to cherry-pick from one branch to another and I like that you can just add an entire directory of files at once unlike some other VCS solutions.

What do you dislike?

Some of the more advanced things you need to do, you'll have to Google to figure out the commands.

What business problems are you solving with the product? What benefits have you realized?

It's pretty much standard these days to use VCS tracking and repositories for software development. Git is the most straightforward to use.

Git review by Jorge P.
Jorge P.
Validated Reviewer
Verified Current User
Review Source

"The best tool for version control"

What do you like best?

After using a centralized VCS, Git comes in handy because you don't have such thing as a 'blocked' file in case you need to make a little change in other peoples' files, so you can test your own.

Configuration in both Windows and Linux is plain and straight. Besides, there's this awesome community and documentation online. It's one of the key points I look for when deciding to use a tool for production environments.

What do you dislike?

Git, however, gets really slow when dealing with repositories above 1GB. When you're used to used Git via command console like me, it's pretty troublesome waiting more than a couple of seconds for the operations to take place (because they usually take 1 second).

Recommendations to others considering the product

Git is probably the number-one tool for version control. It has a great community on which you can rely on, and the best thing you could do is learn git from the ground up via bash or command line. Then, start using GUI tools such as Sourcetree, GitHub for Windows, etc. It could be a little slower at the beginning, but it pays off in the long run.

However, the only disadvantage so far is the use of Git for big repositories. If your codebase size (including assets) is greater than 1GB. After that threshold, it starts to go slow. It's not a real issue for some people, but I'm used to get fast response via command line, and it's not easy to deal with those extra 10-15-second commits when you're in a hurry (it usually takes 1-4 for me with a less-than 1GB codebase)

What business problems are you solving with the product? What benefits have you realized?

I'm a game developer, but I've also worked as a web developer.

Git, as a distributed version control system, works really well on remote teams

Git review by Paige P.
Paige P.
Validated Reviewer
Review Source

"Great way to Maintain software"

What do you like best?

It's easy to use from the Command line or a UI. It has a slight learning curve especially when coming from SVN since it handles Branching and commits a bit differently. There's a few different ways to use Git which is a great feature but its important to find out which ways work best for your company and your environment. Working in separate branches is seamless and easy.

What do you dislike?

Logs can get messy. Especially since Git uses merging by default instead of rebasing so there's a lot of "merge branchname etc" messages in the log. You can force rebasing with your pull requests etc. You need to come up with a method to work in git so everyone is on the same page.

Recommendations to others considering the product

Look into best practices for committing branches to master to get rid of noise from your logs.

What business problems are you solving with the product? What benefits have you realized?

Collaboration and collisions during collaboration are some of the biggest problems developers face. If you share code via zip files or dropbox, you're doing it wrong and should look into git immediately. There's so many resources out there to help with other things needed to help teams run smoothly (such as github for visualizing changes and pull request reviews etc). It also helps working across multiple machines when working along and working in increments and allowing the ability to rollback easily when a change doesn't act as expected etc.

Git review by Tyler S.
Tyler S.
Validated Reviewer
Verified Current User
Review Source

"Version Control at its best"

What do you like best?

That I can version control all my projects, but also have my team use them as well. The collaboration part of our company is huge when working on multiple projects with multiple staff.

What do you dislike?

There are a lot of commands that you have to memorize but once you start learning them they can become easy.

Recommendations to others considering the product

If you need version control and team collaboration then look to Git. It may be a bit of a challenge at first to learn but once you get the hang of it you wont look back.

What business problems are you solving with the product? What benefits have you realized?

Collaboration between staff and version controlling our projects so we don't lose them is huge.

Git review by Ravikiran R.
Ravikiran R.
Validated Reviewer
Verified Current User
Review Source

"Best versioning tool in the market"

What do you like best?

Best distributed version control systems.

Easy to create branch and tags

Good command line tools and options

Easy to compare the versions

What do you dislike?

Once we push the commit with the message, it is very difficult to change the commit message. But there is a provision but it is took long

Recommendations to others considering the product

Best versioning system in the market

What business problems are you solving with the product? What benefits have you realized?

It is not tightly coupled with one server. There are multiple replicas available in the organisation. This will help not to lose the VCS. Easy to maintain

Git review by Administrator in Computer Software
Administrator in Computer Software
Validated Reviewer
Verified Current User
Review Source

"Git is open"

What do you like best?

Git is open which allows your business process dictate your source work flow and not the other way around.

It is distributed making it very unlikely that you will lose source.

What do you dislike?

The name rebase is awful and it can get confusing through all of the gui tools.

Git hooks and attributes can't be applied globally and must be configured for every repo.

What business problems are you solving with the product? What benefits have you realized?

It generally solves the business problem of source control work flows. The key benefits realized are easier continue uous delivery pipeline management with auto tagging tools and release management. Thought it does require some tools outside of git to make the artifacts and deployment git is by far the easiest to accomplish end-to-end delivery.

Git review by Gerardo Esteban C.
Gerardo Esteban C.
Validated Reviewer
Verified Current User
Review Source

"I use Git Everyday as a personal goal to complete as a prove that I code every day."

What do you like best?

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.

What do you dislike?

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.

Recommendations to others considering the product

Learn to work well with Git, let some of your projects as open source, so other can learn from you, and you always will find someone more intelligent than you so there is an opportunity for that person to help you.

What business problems are you solving with the product? What benefits have you realized?

I learn a lot working and coding with other persons, those are the big benefits. By other hand when you work remote it is important to be very proficient with Git because it is the only way you're able to work remote, from home.

Git review by User in Medical Devices
User in Medical Devices
Validated Reviewer
Review Source

"My Favorite Revision Control System"

What do you like best?

Git is a full-featured revision control with a large user base and an immense variety of related tools. In my experience, it is the best tool for collaborative coding, especially when working with remote team members. I prefer to work with the GIT bash while others may prefer GUI facades.

What do you dislike?

Git has a steep learning curve. If you do not keep your process simple, then you can run into a lot of sticky situations. It can also be difficult to remember all the steps to do fairly simple things.

Recommendations to others considering the product

While there are a plethora of online resources, seek out current users to get some hands on training from.

What business problems are you solving with the product? What benefits have you realized?

Our team needed a tool to facilitate collaborative coding that integrates with remote storage and issue management systems.

Git review by Josh T.
Josh T.
Validated Reviewer
Verified Current User
Review Source

"A tool that I can't live without"

What do you like best?

It's great how easy it is to keep track of your changes, make working together as a team easy and easy to rollback changes and keep track of changes.

I also like how well supported it is across every service. Git is the standard VCS.

What do you dislike?

Not much really. Some of the commands aren't always the most intuitive.

Recommendations to others considering the product

Start of simple, then as you need learn all the other commands that are available such as rebasing and branching.

What business problems are you solving with the product? What benefits have you realized?

Git makes working as a team simple, and helps us keep track of all changes that we make to our work.

Git review by Munendra S.
Munendra S.
Validated Reviewer
Verified Current User
Review Source

"Git- Best Version Control System"

What do you like best?

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.

What do you dislike?

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.

Recommendations to others considering the product

Best available Distributed Version Control system. If you need to maintain source code or collaborate on a project, use Git. Git is flexible, has amazing features. It has low delay for push and pull operations.

What business problems are you solving with the product? What benefits have you realized?

Git makes version control easier. Git is distributed hence parallel development is possible. Currently, We are using Git for controlling source code of software in development. Teams are finding easier to manage the code base using Git.

Benefits:

Rollback to previous commits

Difference between versions

Open source community help

Git review by Andrei D.
Andrei D.
Validated Reviewer
Verified Current User
Review Source

"Minutes to hop in, days to adapt, years to master"

What do you like best?

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.

What do you dislike?

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".

Recommendations to others considering the product

Consider Mercurial first. It covers absolute most use cases you'll need with plugins distributed with it (all you have to do is to enable them), yet, though, not supported by various 3rd-party services as much as Git is.

If you chose to stick with Git, well, it's another story:

* Get some good and verbose workflow that covers as much "something gone wrong" cases as possible. Atlassian got nice comparison for you — https://www.atlassian.com/git/tutorials/comparing-workflows

* Get used to Git internals' terminology that sometimes sounds just like something you've familiar with but isn't in fact: e.g. "object", "tree", "blob". You'll need it when you'll face issues which you most certainly will.

* Fastest way to get working recipe is google "git how to <thing you want to do in plain english>"

What business problems are you solving with the product? What benefits have you realized?

Contributing changes to projects in Git repositories

Git review by Cesar I.
Cesar I.
Validated Reviewer
Verified Current User
Review Source

"The best source versioning tool"

What do you like best?

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.

What do you dislike?

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.

Recommendations to others considering the product

It's better to start by using a UI to handle the repositories and a web based service like github for a central repository before diving into more advanced usage.

What business problems are you solving with the product? What benefits have you realized?

Controlling source code it's central to any software development practice and git solves that problem like no other software could before (maybe only mercurial can challenge git in that area).

Git review by Aniruddh C.
Aniruddh C.
Validated Reviewer
Verified Current User
Review Source

"Git removes all barriers to collaboration and code reviews!"

What do you like best?

You can create feature branches, thus being able to work on multiple features (or versions of features) at once. This makes it easier to do code reviews, to apply other's changes, etc.

It's easy to revert a commit, as compared to SVN

What do you dislike?

It has a learning curve. The concept of branches etc are not intuitive to a new user.

Rebasing is tricky, and conflict resolution is less intuitive than in SVN.

Recommendations to others considering the product

Branching is key!

Remember that Git is has difficult to use tooling on Windows systems, and that it has a learning curve.

What business problems are you solving with the product? What benefits have you realized?

Git makes it easy for many developers to work on one project at once. I work on a number of distributed projects with numerous daily commits, and I've found that Git has allowed me to realize the benefits described above as well as being able to allow for more transparent code check-in processes. It also allows for a more stable codebase .

Kate from G2 Crowd

Learning about Git?

I can help.
* We monitor all Git reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.