Try our new research platform with insights from 80,000+ expert users
Senior manager at Softstoneinc
Real User
Top 5
The solution is stable, easy to use, and it can be used for application development
Pros and Cons
  • "The product is easy to use."
  • "The price could be improved."

What is our primary use case?

I use the solution for application development.

What is most valuable?

The product is easy to use.

What needs improvement?

The price could be improved.

For how long have I used the solution?

I have been using the solution for almost ten years. I am using the latest version of the solution.

Buyer's Guide
Git
November 2024
Learn what your peers think about Git. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.

What do I think about the stability of the solution?

I like the product’s stability. I rate the stability a nine out of ten.

What do I think about the scalability of the solution?

The tool is scalable. Five people in our company are using the solution. It is not used extensively in our company.

How was the initial setup?

The initial setup was straightforward. The deployment took five minutes.

What about the implementation team?

I could deploy the product by myself. I used GitHub Actions for deployment. We need one person to deploy and maintain the product.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

People should use the solution because it is easy to use. Overall, I rate the solution a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Senior Developer at SmartStream Technologies ltd.
Real User
Top 5
A standard and open-source product with features like git clone
Pros and Cons
  • "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."

What is our primary use case?

We use Git for our code. 

What is most valuable?

It is a pretty standard product with features like git clone and development branches. 

What needs improvement?

Git is mostly command based and needs to have a helpful user interface. 

For how long have I used the solution?

I have been working the solution for the last three years. 

What do I think about the stability of the solution?

Git is highly stable and I would rate it a ten out of ten. 

What do I think about the scalability of the solution?

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. 

How are customer service and support?

We don't connect with the support team since all the information is available on the internet. 

Which solution did I use previously and why did I switch?

We switched to Git because it supports multiple vendors. 

How was the initial setup?

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. 

What about the implementation team?

We did the product's deployment in-house. Users can do it by themselves.

What's my experience with pricing, setup cost, and licensing?

Git is free and you don't have to pay for it. 

What other advice do I have?

I would rate Git a nine out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Git
November 2024
Learn what your peers think about Git. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
reviewer2072055 - PeerSpot reviewer
Consultant/Software Engineer at a computer software company with 10,001+ employees
Real User
Top 20
CLI and GUI-supported; stable and scalable
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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 is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using Git for four years.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

Which solution did I use previously and why did I switch?

Prior to Git, I used TortoiseSVN.

How was the initial setup?

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.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer2198715 - PeerSpot reviewer
DevOps Engineer at a tech services company with 51-200 employees
Real User
Top 5
A solution useful for creating and uploading codes with ease
Pros and Cons
  • "Git is a stable solution. Stability-wise, I rate the solution a ten out of ten."
  • "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."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using Git for four years. Also, I am using the solution's latest version.

What do I think about the stability of the solution?

Git is a stable solution. Stability-wise, I rate the solution a ten out of ten.

What do I think about the scalability of the solution?

I don't think that it is even possible to count it as a scalable tool.

How are customer service and support?

I never tried to reach tech support.

How was the initial setup?

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.

What was our ROI?

I think it's a good investment, but I'm using the free version of the solution.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Matt Hardy - PeerSpot reviewer
Infrastructure Manager/Deployment Manager at Hivedome Consultancy Services
Real User
Top 5Leaderboard
It has a large community, so there are lots of resources
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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.

What is most valuable?

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. 

For how long have I used the solution?

I have used Git for about three years.

What do I think about the scalability of the solution?

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. 

How was the initial setup?

Git is easy to set up. I've done it multiple times on various systems, and it only takes a few minutes. 

What other advice do I have?

I rate Git eight out of 10. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
VenkateshK4 - PeerSpot reviewer
Digital Transformation Specialist at Technovert
Real User
Top 5
Straightforward setup but not user-friendly
Pros and Cons
  • "The repository management and check-in/check-out commands are the most valuable features for ensuring secure code."
  • "It's not very user-friendly."

What is our primary use case?

Version control and repository management are the main use cases for Git.

What is most valuable?

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.

What needs improvement?

It should be more user-friendly. Git provides important commands for projects. It's not very user-friendly, but it's okay.

For how long have I used the solution?

I have been using this solution for one year. We're using the test version. It's integrated with TSS.

What do I think about the scalability of the solution?

There are 50-60 users in my company. We use it based on the use case.

How was the initial setup?

It's straightforward. It takes around ten to fifteen minutes to set up.

What about the implementation team?

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.

What other advice do I have?

Overall, I would rate it a seven out of ten. I prefer using other tools that are more user-friendly.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Nithya P - PeerSpot reviewer
DevOps Engineer at zelarsoft
Real User
Top 10
Centralized code access with strong version control and remote availability
Pros and Cons
  • "The best feature is that we can access it from anywhere if we have GitHub credentials."
  • "There is nothing that could be improved at this time."

What is our primary use case?

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

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

There is nothing that could be improved at this time.

For how long have I used the solution?

I have been using Git for almost three years now.

What do I think about the stability of the solution?

Git is very stable. It never breaks down.

How are customer service and support?

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

How was the initial setup?

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

What other advice do I have?

I would recommend Git to other people. I'd rate it nine out of ten.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Sedki Ltifi - PeerSpot reviewer
Software Engineer Intern at COSMOS Lab, ENSI, University of manouba, Tunisia
Real User
Top 20
An useful and stable version control solution that finishes projects rapidly
Pros and Cons
  • "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."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How was the initial setup?

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.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Git Report and get advice and tips from experienced pros sharing their opinions.
Updated: November 2024
Product Categories
Version Control
Buyer's Guide
Download our free Git Report and get advice and tips from experienced pros sharing their opinions.