Git Reviews

We use the product for software development and version control. It helps us to maintain a safe repository of our development. 

Git offers the ability to roll back to the previous version. You can also track all the small changes that you do. 

The tool is complicated for a beginner. You need to have some training to use it. It is also hard to find a parameter. 

I have been working with the solution for seven years. 

The product is stable. 

There is no technical support since we use the open source version. We find support mainly on the forums. 

We use the open source version. 

I would rate the product an eight out of ten. The product is the best in the industry. 

Git is used for version control.

Our extensive IT department collaborates on various projects, utilizing Git to manage versions effectively. One significant advantage is the ability to maintain multiple versions of the same code, even when offline. This is particularly beneficial in scenarios where internet connectivity is not available, enabling individuals to work on their code seamlessly. Ultimately, this is a crucial benefit for our team's productivity and market competitiveness.

All of the features in Git are useful.

The solution could improve by having more customization.

I have been using Git for a few years.

The stability is good.

I rate the stability of Git a ten out of ten.

We have approximately 500 people using the solution.

The solution is scalable.

I have not used the support.

I have used solutions prior to Git.

The setup of Git is straightforward. The time it takes to set up depends on the size of the project.

When we're doing things manually, but now we use automation tools. When there is a request made it is automated and deployed in the project.

We did the implementation in-house. We have a team that handles the implementation.

A few people in each team have to do the maintenance of the solution.

I would recommend people start using Git. Users can work on an offline copy without internet connectivity and later sync their changes once online. This process is effortless and speedy. Additionally, it is highly secure. After setting up an Azure account, integration with other tools is possible, allowing for continuous integration and deployment.

I rate Git out of ten.

We use the tool to store codes. 

Our team members can work together and save the code in a single repository. 

The product needs to improve its UI. 

I am using the tool for four to five years. 

The product is stable. 

My company has more than 1000 users for the solution. 

The software's technical support is good. 

Positive

The product's initial setup is easy. 

The tool is an open-source product. 

I would rate the product a ten out of ten. 

I use the solution for application development.

The product is easy to use.

The price could be improved.

I have been using the solution for almost ten years. I am using the latest version of the solution.

I like the product’s stability. I rate the stability a nine out of ten.

The tool is scalable. Five people in our company are using the solution. It is not used extensively in our company.

The initial setup was straightforward. The deployment took five minutes.

I could deploy the product by myself. I used GitHub Actions for deployment. We need one person to deploy and maintain the product.

The tool is not expensive. I rate the pricing a three or four out of ten on a scale where one is cheap and ten is expensive.

People should use the solution because it is easy to use. Overall, I rate the solution a nine out of ten.

Git is used to develop software.

Git's learning curve is shallow, making the solution easy to use after a few tutorials.

I would like more documentation.

I have been using Git for nine months.

Git is stable.

Git is scalable.

I am satisfied with the technical support.

The more we do it, the easier the setup becomes, but the first few times were not easy. At most, it takes a couple of days to implement. 

I rate Git an eight out of ten.

I'm doing little projects to teach myself things and storing them in a Git repository. We have about 20 users at my company. We're open to using it more.

Git is a product everyone uses, so it's almost inescapable. I like the fact that there is a large ecosystem around it. You can bolt various graphical user interfaces onto it or sign up for various repositories like GitHub and AWS CodeCommit. Git has a large community, so there are lots of resources and knowledge bases you can use. 

I have used Git for about three years.

I rate Git seven out of 10 for scalability. The scalability could be better. I think it requires some discipline to have large teams working on the same project without facing problems merging code. I'm using Git for personal projects, but I know companies face merge conflicts when more than one person is working on code simultaneously. 

Git is easy to set up. I've done it multiple times on various systems, and it only takes a few minutes. 

I rate Git eight out of 10. 

I use the solution for website management. 

The tool's user interface is terrible. It needs to be more user-friendly. 

I have been using the product for ten years. 

I used a version control software called Bazaar. I switched to Git since everyone is using it. 

The tool's setup is straightforward. I could complete the solution's deployment in two minutes. 

The tool is free. 

I would rate the solution a five out of ten. There are better solutions out there than Git. 

We use Git for the desktop to maintain some versions of the codebase.

Git is easy to manage, which is one of the main features. Also, the codebase is a major feature. It is helpful for me and easy to manage the interface we are using from development to production. So we manage the versioning of codebases.

The price is an area that needs improvement.

The process of raising a pull request could benefit from some improvement. Currently, when a pull request is created in an organization, a branch is also created. However, each pull request must be individualized to a specific branch. If another person raises a pull request under the same ID assigned to the previous person, and both parties modify the tool, their changes will be grouped together in the same request until it is closed, which is an issue. Therefore, it would be beneficial if pull requests were individualized to each user so that any modifications made are attributed to the specific user's pull request.

I have been using Git for a year. Also, I don't remember the version of the solution I am using.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a ten out of ten.

The solution's initial setup process was easy. It is also easy to get the data. So, even though there are a large number of files, it's easy to clone and get the data details and codebase easily.

The organization looks into the pricing aspects of the solution.

I would recommend the solution to those planning to use it. I rate the overall tool a ten out of ten.