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.

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 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.

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. 

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.

As a student, I used Git to store my source code and versioning. Whenever I do modifications, I can roll back the session if needed. It's the same at work, but we use Git to store documents. 

I like that it's easy to use and because it's accessible from a terminal or a graphical user interface if needed. I also like that we can pass comments from Linux if required.

Synchronization could be better. Sometimes when you create a branch and merge it into another branch, I think it's a bit complex for no reason. The initial setup is also tricky when you do it for the first time.

I have been using Git for almost ten years.

Git is a stable solution. I have never had a problem with this solution.

On a scale from one to ten, I would give Git a nine.

I think Git is scalable. We were always a team of five to ten members, but I think it can handle more. We are an engineering company, and half the company uses Git.

The initial setup is a bit complex if you're doing it for the first time. It also depends on what you're trying to do. If it's just to push code, it's straightforward. But when you have to manage a big project, it can get complicated. For example, you must get information from other branches after setting up your branch. When you merge data, you must ensure you do not touch all this information. Deployment time depends on the project and its scalability.

The deployment steps include creating an account, changing your key, synchronization with the project, creating your branch, and creating your own files and modifying them.

Other members of my team and I implemented this solution.

As a student, I didn't have to pay for the license.

I would tell potential users to read the tutorials and guidebook to understand Git and start doing things inside. You can quickly merge and create branches and versions. You have to be trained to use Git; then, it's easy.

On a scale from one to ten, I would give Git an eight.

We primarily use the solution for version control. We use it to control the development version. We use it for scripts or whatever we are deploying. 

The solution allows for very good version control while coding. We can ignore certain versions and create branches out of exactly what we need. 

The repository is great. We can look into it first before creating versions. 

It works with Unix. 

Once we change things, we can test it locally very easily. 

The initial setup is very easy.

It is stable and reliable.

We have found the solution to be stable.

The pricing is reasonable. 

The solution works perfectly fine so far. For the last year, it hasn't given me issues. 

I've been using the solution for one year. 

It's been stable and reliable. There are no bugs or glitches. I'd rate it eight out of ten. It doesn't crash or freeze. 

The solution can scale well. I'd rate the ability to expand eight out of ten. You can expand it easily. 

Most people are using it in my organization. 

We primarily use GitHub. Now we are using Git for version control. 

The initial setup is very straightforward. It's not complex at all. 

You can pay for a subscription. It is an affordable product. 

I'm an end-user. 

I'd recommend the solution to other users. Both Git and GitHub are very useful for development. 

I would rate the solution eight out of ten.