Git Reviews

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. 

We use Git for storing software, development, and tracking versions. We have plans to use it for ODI as well, mainly to unify software version tracking. Although ODI already has its own internal versioning control, we can also transfer it to Git.

The implementation is easy.

The UI can be more user-friendly.

I have been using Git for around four years.

Git is stable.

I believe Git is scalable.

I give Git an eight out of ten.

We have a few hundred end users.

I recommend Git to others.

Git is used for downloading stuff and tracking purposes. It is very simple. In short, I use Git for tracking changes in the computer, which is very simple.

It's a tool for collaboration, and that's what we use it for in our company.

The main problem for me is the frequent upgrades in the solution because every other upgrade is a minefield. When you do the upgrade, there is always something that doesn't work. We have to spend days to correct it. Then, we stop all updates, and we do the updates in six months or a year. There is always a problem, especially if you do an update, since after that, some libraries don't work. We then spend a lot of time trying to fix it. Therefore, the frequent updates are really, really terrible. The aforementioned area can be improved.

I have experience with Git. Also, I don't remember the version of the solution I am using.

It is a stable solution. Stability-wise, I rate the solution a ten out of ten. I may not probably be the right person to evaluate the tool.

Since I am a very simple user of the tool, its scalability is good for me.

In my company, two or three people use the solution.

It is not an extensively used tool in my company, so there are no plans to increase its usage.

I don't need any technical support because one of my colleagues provides the technical support. He had done the setup of Git, and we just used it. If there is some problem with the new version, he will do the setup, and that's enough for me.

I wasn't involved in the setup.

I just tried to use the solution for what I needed.

I would definitely recommend the solution to those planning to use it.

Overall, I rate the solution a ten 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 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. 

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.

Git is mainly used for code repository and version control.

The performance and stability give you very good control. Definitely, its availability is another valuable feature. 

There is room for improvement in the pricing model of Git. Maybe providing a cheaper version for individual users.

I have been using Git for twelve years. I am using the latest version of Git. 

The stability of the solution is good. I would rate it a ten out of ten. 

The scalability of the solution is good. I would rate it a ten out of ten. There are around 250 users in my company. It is extensively used in our organization. 

The cloud-based version doesn't require anything; just an account creation. Moreover, maintenance is minimal. 

On a scale of one to ten, I would say anyone with basic technical knowledge of three can use it, including engineers and developers with one or two years of experience. 

The ROI is good.

There are free versions available, but if required, you need to pay for licensing.

We used SVN, but very minimally. One reason we switched to Git was that it had a cloud version, while SVN was an on-prem solution.

I would definitely recommend using this solution. 

Overall, I would rate the solution a nine out of ten. 

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.

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.