Git Reviews

We use the solution for two purposes: first, we collaborate with the DevOps team, sharing our code; and second, we commit to a local repository, then push it to the distribution repository.

The most valuable feature is having access to the local country repository even if we have problems with distance access.

The UI can be more user-friendly.

I have been using the solution for two years.

I give the stability a ten out of ten.

I give the scalability a nine out of ten.

We have thousands of users.

We switched to Git because we had distance access issues with our previous solution.

I give the solution an eight out of ten.

I recommend the solution to other users. 

We use Git for version control for programs. 

To have programming projects and keeping track of the copays is always it's always nice to have to be able to reverse changes if they don't work.

I am doing my CV and I am also tracking it with GIt.

I believe it is beneficial to maintain a detailed log or history of who did what to a project and which user committed to the change.

The program is run from your shell and I am comfortable with that.

You have Git Lab as a platform, which is just Git with a web interface. I believe that is already well integrated.

More security is always welcome in my opinion.

I have been working with Git for two years. I use it occasionally.

I am working with the most recent version.

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

In my opinion, Git is a scalable solution.

It is used for Linux, which I believe is the largest open-source project we have running right now.

I don't believe they offer technical support.

I have used Confluence and Jira from Atlassian.

The initial setup is straightforward. You initialize the repo in your code base, and you start committing changes.

It doesn't take very long to deploy it, a few seconds. It's a single connection.

It can be deployed by anyone who is using it.

Git is completely free.

I would definitely recommend using Git.

My advice to others is that it is a good idea to read the manual.

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

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.

I use Git to store our code and maintain different versions, and for some projects, we use CI/CD as part of GitHub.

We centralize all our code in Git, which makes it very useful. Having the code centralized means we can easily access it and control its version efficiently.

The best feature is that we can access it from anywhere if we have GitHub credentials. There is also a private option where our code is accessible only to our organization. Additionally, if there are issues with a local machine, the code can be pulled from GitHub anytime, anywhere, which is another great option.

There is nothing that could be improved at this time.

I have been using Git for almost three years now.

Git is very stable. It never breaks down.

I never had to contact the Git support team for any reason.

The initial setup is easy to use. Anyone who needs version control systems can use it.

I would recommend Git to other people. I'd rate it nine 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 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.