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 are using Git for development. We are cloning the code, pushing code, and raising pull requests. We use it for the typical Git workflow for development.

The solution has improved our company because I no longer have to copy the code on my own and keep it in a safe folder. This solution is organized and it's very useful in a team.

The most valuable feature of Git is the ease of tracking in time what the snapshot of the code was at a particular moment. The versioning is good.

Git could improve the merge conflicts. 

In a future release, the user interface should be easier to use and more intuitive.

I have been using Git for approximately three years.

Git is highly stable.

I have not used the support from Git.

I have not used a similar tool prior to Git.

There is only an online deployment of Git and it belongs to Microsoft.

We have received a return on investment using this solution.

There are some extra costs to Git, but it depends on your use case.

My advice to others is Git is the industry standard for source code versioning and my recommendation for them is to learn it and use it.

I rate Git a nine out of ten.

We use the solution for code management to store and version the code. It is the standard service we use for developing applications and infrastructure services.

You can have a central code repository using Git and have local code branches. 

I would like to see less updates with the product. 

I have been using the product for a couple of years. 

I rate Git's stability a ten out of ten. 

We Google the queries and look for support in communities. 

Git's deployment is straightforward. You need to run a few commands until you get a central repository. 

We can do the deployment ourselves. 

I rate Git a ten 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.

The most used case for it is managing code versions when working on a project with many developers. After we merge it, the dash is merged in the master dash. Next, when we merge its branch to replace it with the master and resolve conflicts, we collaborate to finish the project.

Code versioning, for example, we work in the branch and want to come back to this branch another time.Git is a very useful tool, helpful to collaborate with other members in the group to finish more rapidly our work.

About the configuration it is a little bit difficult, it can be improved.

I have been using the solution for the last two years.

It is a stable solution. Never faced any bugs or glitches. I rate the stability of the solution an eight out of ten.

It is not a very scalable solution. It is not a good experience to manage large scalable products. I have moderate experience in managing large projects on Git. One thousand users are using the solution regularly. I rate the scalability of the solution a seven out of ten.

The initial setup of Git can be difficult but once you master the solution it is a useful tool and works on many difficulties by rapidly completing the task.

I advice everyone to learn about Git as it is a very useful solution and help in working on projects more rapidly which otherwise would have taken time. I rate the overall solution an eight 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.

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 am an engineer and I am using Git for research. I follow the event issues that can take place.

The most valuable feature of Git is its reliability and user popularity.

If the solution could provide more language support options such as Korean, it would be helpful.

I have been using Git for approximately three years.

The stability of Git is good.

We have approximately 500 users using this solution in my company.

I have not used the technical support of the solution.

I have not used similar solutions to Git.

There is no installation for the solution because it is cloud-based.

I would recommend this solution to others. It is popular.

I rate Git an eight out of ten.