Git Reviews

Our primary use case is source control and code checking. We used it as version control for collaboration projects. The most important use case is being able to look into the code. Somebody can publish the code publicly in a standard format, which organizes the standard format of code. Then, the team follows the structure of the README file and the code structure.

I also used this solution to make my resume stand out.

What I find the most valuable about Git is that it is CLI and GUI-supported. People who do not like using the CLI mode can use the GUI mode. The solution also now comes with the VS (Visual Studio) code. The ID comes with the Git adapter. This is handy, that is why there is wide adoption of Git.

We have had a mixed reaction to the newly-introduced code pilot. It improved the coding but was also gave too much to the AI and people are concerned that Git Copilot could result in a lot of job losses.

I have been using Git for four years.

I would rate the stability of this solution a 10, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the scalability of this solution a 10, on a scale from one to 10, with one being the worst and 10 being the best.

Prior to Git, I used TortoiseSVN.

I would rate the initial setup process a four, on a scale from one to 10, with one being the most difficult and 10 being the easiest. The reason for this rating is that once there are conflicts, it takes a lot of effort to resolve them.

For the people looking to use this solution, I would say, go through some of the basic videos and learn the basic commands to get started and then explore more of the features. Get some hands-on experience and collaborate with others to find out more about the solution. 

Overall, I would rate Git a nine, on a scale from one to 10, with one being the worst and 10 being the best.

We use this solution to host our software, and where we need to develop new features and new functionality, we create new branch from our existing software, work on our branch, develop it, test it, validate it, and then merge it with the master or main software.

The best thing about this solution is that it can be learned very quickly, and used very easily.

We would like to see tutorials added to the product, for new users to follow so that they can optimize their use of the solution.

We have been using this solution for more than three years.

We have found this to be a very stable solution.

This solution is easily scalable, and can comfortably handle multiple users accessing the system at the same time.

This solution provides a lot of support online, that gives quick access to fixes for the majority of issues.

The initial setup of this solution is very easy and straightforward. New users download the interface, using a simple command on the command line, then begin using it.

This is an open-source solution, so there are no licensing fees associated with it, and no extra, 'hidden' charges.

We would recommend new users to start with the areas of this solution that have a user interface. This has a step-by step guide available that will allow them to get used to the product.

I would rate this solution a 10 out of 10.

I use Git for version control. It helps us to distribute development and manage source code. 

The tool's most valuable feature is branch workflows. 

I believe there is room for improvement in preventing work loss due to conflicts or overwriting. Another area for improvement could be implementing features for automated code verification within Git. 

I rate the solution's scalability a seven out of ten. My company has eight developers using it. 

I haven't contacted the tool's technical support. 

I would rate my experience with the initial setup of Git as a seven or six out of ten. It has clear documentation and takes one or two hours to deploy. The deployment process involved installing Git, creating a project in Git, and configuring it with administrative privileges. Then, the steps included preparation, conversion, synchronization, and migration. This set up the repository, allowed for safe changes, and enabled inspection of the repository.

I rate the tool's pricing a five out of ten. 

I can provide support and control over the development teams, such as developing scripts for managing code or administering Git repositories for all members. However, we may need an extra week or two for additional training.

According to my opinion, every programmer should use Git. 

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.

We use Git for configuration management.

Git is an easy-to-use solution that can be used for parallel working.

Git's user interface could be improved.

I have been using Git for almost eight years.

Git is a stable solution.

Git is a scalable solution. Around 2,000 users use the solution in our organization.

Before Git, we used other solutions. We switched to Git for better stability.

Git's initial setup is a bit complex and not easy.

The solution's initial setup can be done through an in-house team, which could take weeks. It would help if you did the basic learning first before deploying Git.

I would recommend Git to other users.

Overall, I rate Git an eight 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.

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.