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 easy to use. With the help of a few online tutorials, a person can understand how it works.

The platform could have a feature for monitoring data recovery similar to Azure.

We have been using Git for nine months.

It is a stable product.

It is a scalable product.

Git’s technical support services are satisfactory.

Git’s initial setup has 60% complexity. In the beginning, it was not easy to set up for us. Although, with more experience, it has become more accessible. It takes a few days to complete. We have to make sure we have covered all the essential things.

The platform is less expensive.

I rate the product an eight 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.

We use Git for our code. 

It is a pretty standard product with features like git clone and development branches. 

Git is mostly command based and needs to have a helpful user interface. 

I have been working the solution for the last three years. 

Git is highly stable and I would rate it a ten out of ten. 

The solution is highly scalable and I would rate it a ten out of ten. My company has 500 users for it. We use it on a daily basis. 

We don't connect with the support team since all the information is available on the internet. 

We switched to Git because it supports multiple vendors. 

Git's setup is easy and I would rate it a nine out of ten. There are documents available with plenty of information. Hence, if there are any issues, you can sort them out. The tool's deployment is fast. 

We did the product's deployment in-house. Users can do it by themselves.

Git is free and you don't have to pay for it. 

I would rate Git a nine out of ten. 

I use Git to manage my personal projects involving web basics, web design, and web pages. I am able to clone most things using Git.

I use it for web design version control. I also conduct a lot of research on open-source technologies that we can install using Git.

I have discovered that most of the solutions offered on Git can also be found on Docker.

It would be preferable if the updates could be completed at a faster pace.

Version control is beneficial as it allows me to keep track of all the modifications I have made to the applications.

I have no problems with Git and prefer using the Terminal Point of View for its high speed.

I attempted to use an alternative user interface, but it was too sluggish for me. I discovered that the Terminal is more efficient and rapid for executing events on Linux and Ubuntu. Its swiftness in event deployment is remarkable.

I have been working with Git for three or four years.

I update the versions every now and then.

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

Performing periodic updates can be time-consuming, but it is not a significant concern as it doesn't disrupt my schedule. However, I do need to make a conscious effort to initiate the updates.

Git is a scalable solution.

Another advantage is that any team can work on it effortlessly, even large teams, making it highly collaborative.

I am currently using it and there are only a few people who I would like to share my changes with. With the current capability to view the modifications I have made, I am able to open it and see the updates for my team.

I am not planning to increase my usage at this time.

I have not contacted technical support.

Ever since I began my training in web and development, it was the easiest platform for me to use and was the only one that was introduced. I did not explore others.

The initial setup is straightforward.

The deployment process was quick for me. I was able to execute it on my personal computer and also clone it to my personal Git account.

I am not required to pay due to the small number of users we have. 

We have a small user base, and we are not using the enterprise version.

I highly recommend others use Git for version control.

Because of its version control, I would rate Git a ten out of ten.

I use Git mainly to create new reports to store my project and to keep track of the changes I made in my code. So these are the main reasons why all people use Git.

I did use it in my organization as well. I did use it personally, but it was very easy to use it by yourself, especially when you create and upload your code, it's easy. If other people are included in their project, you're going to have to make merge requests to merge the code you made, and the code your colleagues have made. So it's a little bit complicated. So, when I started using it in my organization, It was a bit messy, but I finally got it.

Speaking about features, it helps to keep track of your code if it changes, especially to find who made the changes. The solution also makes it easy for other people to change your code.

I don't think it does need any improvement for now since Git is a free, open-source project.

To be honest, I didn't even get close to seeing all its current features. So, I can't imagine any new features that I would be able to recommend.

If it was possible to pay for a Git solution, I would pay for it. However, it's difficult in my country. So I mainly enjoy the free solution.

I have been using Git for four years. Also, I am using the solution's latest version.

Git is a stable solution. Stability-wise, I rate the solution a ten out of ten.

I don't think that it is even possible to count it as a scalable tool.

I never tried to reach tech support.

GitHub and GitLab were pretty good repositories for Git servers. So, I was using the solution on the cloud.

I did not deploy it. I was using already deployed solutions like GitLab and GitHub. I never did even try to deploy it.

I think it's a good investment, but I'm using the free version of the solution.

My recommendation to others to use the solution would depend on their usage. If it's for their personal use, it's going to be easy. But if he was going to use it in an organization or for a personal project with a lot of friends or colleagues, then that would be a different story. You need to be concentrated, and I think a lot before making any changes to the code because every mistake can create a lot of problems.

I rate the overall solution a nine 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. 

Version control and repository management are the main use cases for Git.

The repository management and check-in/check-out commands are the most valuable features for ensuring secure code. It's a client-side tool that we install in our local company and connect to the cloud product for use cases.

It should be more user-friendly. Git provides important commands for projects. It's not very user-friendly, but it's okay.

I have been using this solution for one year. We're using the test version. It's integrated with TSS.

There are 50-60 users in my company. We use it based on the use case.

It's straightforward. It takes around ten to fifteen minutes to set up.

The deployment can be done in-house. The deployment process is good but there may be a learning curve for some users. However, it could benefit from additional hands-on experience, particularly for enterprise-level usage.

Overall, I would rate it a seven out of ten. I prefer using other tools that are more user-friendly.