Eaton Tripp Lite Series DVI Dual-Link Extension Adapter Cable with 45-Degree Left Plug (DVI-D M/F), 1 ft. (0.3 m) - DVI
$34.48
$16.95
Mfg # P562-001-45L
CDW # 1032686
| UNSPSC 26121600
Quick tech specs
- 1 ft DVI-D Male to DVI-D Female adapter cable is the ideal solution for those tight spaces where a standard straight DVI cable will not fit
- Saves wear and tear on your equipment connector
- For use w/ Digital CRT displays/ Flat Panel Displays/ HDTV and Projectors
- Tripp Lite is now a part of Eaton
- For use w/ Single or Dual TMDS Link specified equipment
- Superior molded cables w/ foil/braid shielding for maximum EMI/RFI protection
- DVI cable/ DVI-D M/F cable/ DVI-D to DVI-D cable
Know your gear
Tripp Lite's 0.31 m (1-ft.) DVI-D Male to DVI-D Female adapter cable is the ideal solution for those tight spaces where a standard straight DVI cable will not fit. The adapter also saves wear and tear on your video cards connector. This cable features Gold connectors and contacts, fully molded ends, and double-shielded cable.
Add to Compare
Enhance your purchase
Tripp Lite 1ft DVI Dual Link Digital Extension Cable 45 degree Left Plug 1' is rated
4.50 out of
5 by
37.
Rated 5 out of
5 by
Nithya P from
Centralized code access with strong version control and remote availability
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
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2024-09-18T00:00:00-04:00
Rated 5 out of
5 by
Hari Kathireshan from
An easy-to-use solution that can be used for configuration management
What is our primary use case?
We use Git for configuration management.
What is most valuable?
Git is an easy-to-use solution that can be used for parallel working.
What needs improvement?
Git's user interface could be improved.
For how long have I used the solution?
I have been using Git for almost eight years.
What do I think about the stability of the solution?
Git is a stable solution.
What do I think about the scalability of the solution?
Git is a scalable solution. Around 2,000 users use the solution in our organization.
Which solution did I use previously and why did I switch?
Before Git, we used other solutions. We switched to Git for better stability.
How was the initial setup?
Git's initial setup is a bit complex and not easy.
What about the implementation team?
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.
What other advice do I have?
I would recommend Git to other users.
Overall, I rate Git an eight out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-07-26T00:00:00-04:00
Rated 5 out of
5 by
Jojo John from
A standard and open-source product with features like git clone
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
Disclaimer: I am a real user, and this review is based on my own experience and opinions.customer
Date published: 2023-07-24T00:00:00-04:00
Rated 5 out of
5 by
Miodrag Milojevic from
Great for storing software, development, and tracking versions
What is our primary use case?
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.
What is most valuable?
The implementation is easy.
What needs improvement?
The UI can be more user-friendly.
For how long have I used the solution?
I have been using Git for around four years.
What do I think about the stability of the solution?
Git is stable.
What do I think about the scalability of the solution?
I believe Git is scalable.
What other advice do I have?
I give Git an eight out of ten.
We have a few hundred end users.
I recommend Git to others.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-07-23T00:00:00-04:00
Rated 5 out of
5 by
LotfiLarbaoui from
Helps to distribute development, do version control and manage source code
What is our primary use case?
I use Git for version control. It helps us to distribute development and manage source code.
What is most valuable?
The tool's most valuable feature is branch workflows.
What needs improvement?
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.
What do I think about the scalability of the solution?
I rate the solution's scalability a seven out of ten. My company has eight developers using it.
How are customer service and support?
I haven't contacted the tool's technical support.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
I rate the tool's pricing a five out of ten.
What other advice do I have?
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.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.Customer
Date published: 2024-05-20T00:00:00-04:00
Rated 5 out of
5 by
Dimitris Iracleous from
A powerful and mature solution that helps to collaborate and eliminate issues with code
What is our primary use case?
The tool is integrated into our environment and transmits our data and code to the repository.
What is most valuable?
Git is a powerful and mature tool that all software engineers use, whether they use it from the command line with the original version or integrate it with various tools. It helps by promoting collaboration and eliminating problems with code in separate locations. This greatly boosts productivity since you're not lost in a massive local repository, and everything remains organized.
Instead of manually finding solutions, AI condenses them. This significantly reduces our design time. By utilizing AI, we can incorporate best practices in analysis, design, and implementation into our projects.
What needs improvement?
Some challenges arise when Git is not used correctly, particularly in managing branches. It's easy to get lost, but these challenges can be overcome with proper management. A common advice is maintaining the repository and ensuring developers are in sync with the production branch. Branches should be promptly merged into development to avoid getting lost in many branches.
For how long have I used the solution?
I have been using the product for five to six years.
What do I think about the stability of the solution?
I would rate Git's stability as a ten out of ten. However, it's crucial for users and developers to maintain their branches responsibly.
What do I think about the scalability of the solution?
I rate the tool's scalability a nine out of ten. Everyone is using Git because it's a central tool. We have about ten teams, each comprising around five people, utilizing it for development.
When I refer to the teams, I'm referring to the technical team. Additionally, we have project managers who typically oversee three or four teams each. Beyond that, we have sector managers responsible for their respective departments. Each department consists of about three to four people who also utilize Git.
How was the initial setup?
The tool's deployment is easy. The developer is responsible for maintaining the working environment on their laptop. Once the work is completed, they submit it to the central repository on GitHub.
What about the implementation team?
We did the deployment in-house.
What was our ROI?
I believe Git is a tool everyone should use because it increases productivity and reduces time. It's widely adopted, and I can't imagine a modern software system that doesn't utilize Git. It is one of the best solutions available.
What's my experience with pricing, setup cost, and licensing?
Git is an open-source software.
What other advice do I have?
I rate the overall solution a ten out of ten. My advice to those starting with Git is not to be afraid to understand how it works. They should establish guidelines for their workflow, including how they create branches and merge, to avoid getting lost. While the tool is not difficult to use, it does require adhering to certain rules.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2024-05-20T00:00:00-04:00
Rated 5 out of
5 by
Vinay Jirgale from
Easy to set up and has useful version control but needs to be more standardized
What is our primary use case?
We create feature branches with the product for our global development. They merge to create a full request, and we can review and merge the code.
What is most valuable?
The version control is quite useful. Each year, we move to a new version to update our code. You can build out branches.
We are able to do effective incremental work and then push new code remotely. We can resolve merge conflicts.
The setup process is pretty simple.
What needs improvement?
There is no standard for managing feature branches. While there are branches created, and they can be reviewed before merging, there isn't yet a standardization, which means the team has to follow up.
New developers sometimes find it difficult to call a review or create a request. They don't necessarily know what to push or if they should be creating feature branches, etc. The should work to make it simpler to use with more standardization to help new users acclimatize faster.
For how long have I used the solution?
I've been using the solution for more than five years now.
What do I think about the stability of the solution?
The stability is okay. I'd rate it six to seven out of ten.
What do I think about the scalability of the solution?
The scalability is pretty good. I'd rate it seven out of ten in terms of its ability to expand.
We have about 50 users or more on the solution right now.
How are customer service and support?
We don't use technical support. If we run into issues, we turn to forums and deal with the community. We can find the answers we need on Google for the most part.
Which solution did I use previously and why did I switch?
We've also used Bitbucket in the past. It has good integration with Jira. I've also used GitHub and GitLab.
Azure DevOps also allows you to host event repos. However, I have not used it much.
How was the initial setup?
It's not too complex to set up. The solution is simple to implement. It can differ from project to project.
What's my experience with pricing, setup cost, and licensing?
We mostly use the free version of the solution. We also use GitLab, which has a licensed version.
What other advice do I have?
I'm a Git user.
I'd rate the solution seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-02-15T00:00:00-05:00
Rated 5 out of
5 by
Emmanuel Uzochukwu from
A shallow learning curve that is easy to use
What is our primary use case?
Git is used to develop software.
What is most valuable?
Git's learning curve is shallow, making the solution easy to use after a few tutorials.
What needs improvement?
I would like more documentation.
For how long have I used the solution?
I have been using Git for nine months.
What do I think about the stability of the solution?
Git is stable.
What do I think about the scalability of the solution?
Git is scalable.
How are customer service and support?
I am satisfied with the technical support.
How was the initial setup?
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.
What other advice do I have?
I rate Git an eight 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
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-07-30T00:00:00-04:00
Rated 5 out of
5 by
MOMEN ABDELSADEK from
Easy-to-use product with good scalability features
What is most valuable?
Git is easy to use. With the help of a few online tutorials, a person can understand how it works.
What needs improvement?
The platform could have a feature for monitoring data recovery similar to Azure.
For how long have I used the solution?
We have been using Git for nine months.
What do I think about the stability of the solution?
It is a stable product.
What do I think about the scalability of the solution?
It is a scalable product.
How are customer service and support?
Git’s technical support services are satisfactory.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
The platform is less expensive.
What other advice do I have?
I rate the product an eight out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-07-30T00:00:00-04:00
Rated 5 out of
5 by
Jue Jung from
The solution is stable, easy to use, and it can be used for application development
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.
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.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-10-06T00:00:00-04:00
Rated 5 out of
5 by
Collette Michaels from
Has a good automated deployment process and good scalability options
What is most valuable?
The features I am most impressed by is the automation, and when we do the pull requests, everything gets indicated on there in terms of the deployment steps and full-on automated deployment. We have found that the standard level for DevOps in terms of automated deployment is 30 minutes. So we actually hit that in 30 minutes, which was great.
What needs improvement?
I would like to see an improvement in the way the product owner can review changes and so forth. But I believe there are licensing costs related to that. It would be better to keep everything simple with one standard license fee.
For how long have I used the solution?
We've been using Git on our premises for about eight months now.
What do I think about the stability of the solution?
There wasn't any instability at all because when we did our first automation deployment, we hit 100% with zero bugs introduced. That was really, really good. I just think we must get the automated testing right. We don't have that many seasoned automated tests and therefore we did all the full-on regression testing that was needed, went into production and had zero defects.
What do I think about the scalability of the solution?
We have about 40 to 50 users and 12 testers, and so far it has been very scalable. We plan to increase our usage in the future.
How are customer service and technical support?
We have monitors in place for our usual business so if anything goes down, there is an immediate response to look at that from a proactive perspective to see what is affected. In terms of from a testing perspective, through change, it is a database issue or anything like that. In terms of support, we have two sections of support. One for terms of DevOps where we have a operations person responsible for this. And when we put the software into production, we have someone on standby to ensure that everything is in perfect working condition.
If you previously used a different solution, which one did you use and why did you switch?
There are other options in the greater part of our environments. But since we were working on Microsoft from the start, it just was easier to continue that way. It was a new department being established and we wanted to start off that way, rather than moving from an old state to a new state. It takes longer and the change management is greater.
How was the initial setup?
Our technical team will be able to tell you exactly, but I believe they found some problems around the installation and so forth. I do know that it took them a while to actually get the automated deployment right before they could actually execute it. Perhaps the developers can make it easier in terms of getting readiness for automation deployment. It was quite complex and it took us about a day and a half. However, if you do a manual deployment, it doesn't take that long.
What other advice do I have?
My advice to others would be to implement it correctly and do whatever your unit test brings back in terms of an approach. Fix that first and then start with your coding. That is how you ensure quality.
I would say that you should start afresh. Instead of trying the squad branching, do the release branching, and work from there. Don't be wary of actually starting on DevOps. Sometimes people are wary of the unknown but it adds a lot of value if you go with the CDCI approach.
It is a great product and my rating is eight out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2019-09-09T00:00:00-04:00
Rated 5 out of
5 by
Yasmine Abib from
A user-friendly distributed version control system that is accessible from a terminal or a graphical user interface
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Git for almost ten years.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How was the initial setup?
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.
What about the implementation team?
Other members of my team and I implemented this solution.
What's my experience with pricing, setup cost, and licensing?
As a student, I didn't have to pay for the license.
What other advice do I have?
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.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-04-02T00:00:00-04:00
Rated 5 out of
5 by
Tin Bùi from
Efficiently keep track of changes and maintain control
What is our primary use case?
The primary use case is to keep track of changes and maintain control, and it helps contain your code and is useful for collaboration.
What is most valuable?
One feature I find valuable is that it's a one-shot solution. Also, every software company has a requirement to use Git.
What needs improvement?
I am trying to understand why they removed the credential because it has been a great feature. But yeah, that's not looking good on me. Moreover, Git should increase security to reduce risk.
Another improvement could be that it is easy to install but complex to set up.
For how long have I used the solution?
I have been using this solution for ten years. We always use the latest version in our company.
What do I think about the stability of the solution?
It is a stable solution that has been fine for me for ten years.
I rate the stability a ten out of ten.
What do I think about the scalability of the solution?
It is a scalable solution. Everyone can use it, and there are over 200 uses in my company.
How was the initial setup?
The initial setup is a bit complex because it is open source.
What about the implementation team?
We deployed it from some commands, which took just a few seconds. It's open source, so there is no need for a consultant.
What other advice do I have?
Many tutorials are available online, and one should search for them and go through them before doing anything.
Overall, I would rate it a ten out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-03-30T00:00:00-04:00
Rated 5 out of
5 by
Claudiu Milea from
Useful time tacking and highly stable
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
Git could improve the merge conflicts.
In a future release, the user interface should be easier to use and more intuitive.
For how long have I used the solution?
I have been using Git for approximately three years.
What do I think about the stability of the solution?
Git is highly stable.
How are customer service and support?
I have not used the support from Git.
Which solution did I use previously and why did I switch?
I have not used a similar tool prior to Git.
How was the initial setup?
There is only an online deployment of Git and it belongs to Microsoft.
What was our ROI?
We have received a return on investment using this solution.
What's my experience with pricing, setup cost, and licensing?
There are some extra costs to Git, but it depends on your use case.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-10-21T00:00:00-04:00
Rated 5 out of
5 by
Mohd Javed from
Easy to set up with good reliability and reasonable pricing
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
The solution works perfectly fine so far. For the last year, it hasn't given me issues.
For how long have I used the solution?
I've been using the solution for one year.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
We primarily use GitHub. Now we are using Git for version control.
How was the initial setup?
The initial setup is very straightforward. It's not complex at all.
What's my experience with pricing, setup cost, and licensing?
You can pay for a subscription. It is an affordable product.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Private Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-02-26T00:00:00-05:00
Rated 5 out of
5 by
Srujan Panuganti from
An excellent open source, software hosting solution that provides strong version control functionality and a user-friendly interface
What is our primary use case?
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.
What is most valuable?
The best thing about this solution is that it can be learned very quickly, and used very easily.
What needs improvement?
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.
For how long have I used the solution?
We have been using this solution for more than three years.
What do I think about the stability of the solution?
We have found this to be a very stable solution.
What do I think about the scalability of the solution?
This solution is easily scalable, and can comfortably handle multiple users accessing the system at the same time.
How are customer service and support?
This solution provides a lot of support online, that gives quick access to fixes for the majority of issues.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
This is an open-source solution, so there are no licensing fees associated with it, and no extra, 'hidden' charges.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-10-26T00:00:00-04:00
Rated 5 out of
5 by
Ben Mbarek from
Reliable, useful tacking, and simple implementation
What is our primary use case?
Git can be deployed on the cloud and on-premise.
What is most valuable?
The most valuable feature of Git is its ability to track updates, such as firmware documentation. Additionally, many people can make changes to code without problems. It is able to solve conflicts very easily.
What needs improvement?
Git can improve the size of the depository it can handle and add the capability to detect the change between common files, such as Excel and PDF documents.
For how long have I used the solution?
I have been using Git for approximately five years.
What do I think about the stability of the solution?
Git is stable.
What do I think about the scalability of the solution?
The scalability of Git is good.
We have only developed using this solution in my company.
How are customer service and support?
I rate the support from Git a three out of five.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We use another solution prior to Git.
How was the initial setup?
Git is not simple to set up.
What about the implementation team?
We did the implementation of Git in-house.
Which other solutions did I evaluate?
We did not evaluate other solutions.
What other advice do I have?
We have one person that does the maintenance of the solution that accesses the cloud services.
I rate Git a ten out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-11-03T00:00:00-04:00
Rated 5 out of
5 by
Grazvydas Govaras from
Helps to store and version the code
What is our primary use case?
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.
What is most valuable?
You can have a central code repository using Git and have local code branches.
What needs improvement?
I would like to see less updates with the product.
For how long have I used the solution?
I have been using the product for a couple of years.
What do I think about the stability of the solution?
I rate Git's stability a ten out of ten.
How are customer service and support?
We Google the queries and look for support in communities.
How was the initial setup?
Git's deployment is straightforward. You need to run a few commands until you get a central repository.
What about the implementation team?
We can do the deployment ourselves.
What other advice do I have?
I rate Git a ten out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2024-01-19T00:00:00-05:00
Rated 5 out of
5 by
Mohammed Fareed from
When two developers are working on the same file, it merges automatically
What is our primary use case?
We have our code on GitHub, and we need to download the code from GitHub. We installed Git on our local system. We can use commands like Git clone to get a copy of the code repository from GitHub on our local system. The latest version I've used is 2.38.
Once the code is on our system, we can do some code changes and local testing independently without affecting the production server. It does not affect GitHub. When we are satisfied with the code changes and testing, we can push our code changes from local Git to the GitHub repository. We have about 10 users on Git.
We plan to use Git more in the future. We will upgrade to GitHub Enterprise, a paid tool. We need an advanced level of Git.
How has it helped my organization?
Git has helped me a lot with development. For example, let's say I want to write a Terraform script to create infrastructure and web app services. First, I will write the Terraform script in my local Visual Studio Code tool. We'll do local testing like boundary value analysis, unit testing, and everything I do. Using Git tools, I can push the code from the local to the production server.
What is most valuable?
I like Git's merging feature. For example, say there is an instance where I am working on the same code as another developer. Git automatically merges the work of two developers on the same file. If I'm working on line 50 and he's working on 60, and we both commit, it mergest automatically.
What needs improvement?
If the file changes are on the same line, we need to resolve a merge conflict manually. Let's say there is a merge conflict on line 50 because we have multiple commits on the same line number. Git could add some artificial intelligence to resolve the conflict automatically. I would also like to see a GUI like Visual Studio Code and Linux has.
For how long have I used the solution?
We have been using Git for the last four or five years.
What do I think about the stability of the solution?
I rate Git seven out of 10 for stability.
What do I think about the scalability of the solution?
I rate Git seven out of 10 for scalability.
How are customer service and support?
I rate Git support seven out of 10.
How was the initial setup?
Installing Git is easy. We can install it with one command. If we are deploying on Windows, you only need to download and double-click. On Linux, we use the Git app to install it with a guest installer. It is deployed on the cloud.
What's my experience with pricing, setup cost, and licensing?
Git is an open-source solution.
What other advice do I have?
I rate Git eight out of 10.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-12-27T00:00:00-05:00
Rated 5 out of
5 by
reviewer2072055 from
CLI and GUI-supported; stable and scalable
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.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-01-25T00:00:00-05:00
Rated 5 out of
5 by
Govind Varma from
Good performance and stable solution
What is our primary use case?
Git is mainly used for code repository and version control.
What is most valuable?
The performance and stability give you very good control. Definitely, its availability is another valuable feature.
What needs improvement?
There is room for improvement in the pricing model of Git. Maybe providing a cheaper version for individual users.
For how long have I used the solution?
I have been using Git for twelve years. I am using the latest version of Git.
What do I think about the stability of the solution?
The stability of the solution is good. I would rate it a ten out of ten.
What do I think about the scalability of the solution?
The scalability of the solution is good. I would rate it a ten out of ten. There are around 250 users in my company. It is extensively used in our organization.
How was the initial setup?
The cloud-based version doesn't require anything; just an account creation. Moreover, maintenance is minimal.
On a scale of one to ten, I would say anyone with basic technical knowledge of three can use it, including engineers and developers with one or two years of experience.
What was our ROI?
The ROI is good.
What's my experience with pricing, setup cost, and licensing?
There are free versions available, but if required, you need to pay for licensing.
Which other solutions did I evaluate?
We used SVN, but very minimally. One reason we switched to Git was that it had a cloud version, while SVN was an on-prem solution.
What other advice do I have?
I would definitely recommend using this solution.
Overall, I would rate the solution a nine out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-05-05T00:00:00-04:00
Rated 5 out of
5 by
Venky-Venkatesh from
With an intuitive interface in place, the tool is extremely easy to manage
What is our primary use case?
We use Git for the desktop to maintain some versions of the codebase.
What is most valuable?
Git is easy to manage, which is one of the main features. Also, the codebase is a major feature. It is helpful for me and easy to manage the interface we are using from development to production. So we manage the versioning of codebases.
What needs improvement?
The price is an area that needs improvement.
The process of raising a pull request could benefit from some improvement. Currently, when a pull request is created in an organization, a branch is also created. However, each pull request must be individualized to a specific branch. If another person raises a pull request under the same ID assigned to the previous person, and both parties modify the tool, their changes will be grouped together in the same request until it is closed, which is an issue. Therefore, it would be beneficial if pull requests were individualized to each user so that any modifications made are attributed to the specific user's pull request.
For how long have I used the solution?
I have been using Git for a year. Also, I don't remember the version of the solution I am using.
What do I think about the stability of the solution?
Stability-wise, I rate the solution a nine out of ten.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution a ten out of ten.
How was the initial setup?
The solution's initial setup process was easy. It is also easy to get the data. So, even though there are a large number of files, it's easy to clone and get the data details and codebase easily.
What's my experience with pricing, setup cost, and licensing?
The organization looks into the pricing aspects of the solution.
What other advice do I have?
I would recommend the solution to those planning to use it. I rate the overall tool a ten out of ten.
Which deployment model are you using for this solution?
On-premises
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-05-05T00:00:00-04:00
Rated 5 out of
5 by
reviewer1829205 from
Feature rich, scales well, and straightforward deployment
What is our primary use case?
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.
What is most valuable?
All of the features in Git are useful.
What needs improvement?
The solution could improve by having more customization.
For how long have I used the solution?
I have been using Git for a few years.
What do I think about the stability of the solution?
The stability is good.
I rate the stability of Git a ten out of ten.
What do I think about the scalability of the solution?
We have approximately 500 people using the solution.
The solution is scalable.
How are customer service and support?
I have not used the support.
Which solution did I use previously and why did I switch?
I have used solutions prior to Git.
How was the initial setup?
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.
What about the implementation team?
We did the implementation in-house. We have a team that handles the implementation.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-05-02T00:00:00-04:00
Rated 5 out of
5 by
Sedki Ltifi from
An useful and stable version control solution that finishes projects rapidly
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.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-06-08T00:00:00-04:00
Rated 5 out of
5 by
Rouissi Iheb from
A solution useful for creating and uploading codes with ease
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.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-06-07T00:00:00-04:00
Rated 5 out of
5 by
Keith Hodges from
A free tool that helps with website management
What is our primary use case?
I use the solution for website management.
What needs improvement?
The tool's user interface is terrible. It needs to be more user-friendly.
For how long have I used the solution?
I have been using the product for ten years.
Which solution did I use previously and why did I switch?
I used a version control software called Bazaar. I switched to Git since everyone is using it.
How was the initial setup?
The tool's setup is straightforward. I could complete the solution's deployment in two minutes.
What's my experience with pricing, setup cost, and licensing?
The tool is free.
What other advice do I have?
I would rate the solution a five out of ten. There are better solutions out there than Git.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-05-15T00:00:00-04:00
Rated 5 out of
5 by
Jerome TOUTEE from
Helps with software development and version control
What is our primary use case?
We use the product for software development and version control. It helps us to maintain a safe repository of our development.
What is most valuable?
Git offers the ability to roll back to the previous version. You can also track all the small changes that you do.
What needs improvement?
The tool is complicated for a beginner. You need to have some training to use it. It is also hard to find a parameter.
For how long have I used the solution?
I have been working with the solution for seven years.
What do I think about the stability of the solution?
The product is stable.
How are customer service and support?
There is no technical support since we use the open source version. We find support mainly on the forums.
What's my experience with pricing, setup cost, and licensing?
We use the open source version.
What other advice do I have?
I would rate the product an eight out of ten. The product is the best in the industry.
Which deployment model are you using for this solution?
On-premises
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-05-11T00:00:00-04:00
Rated 5 out of
5 by
Matt Hardy from
It has a large community, so there are lots of resources
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.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-05-27T00:00:00-04:00
Rated 5 out of
5 by
Mbaye NDIAYE from
A stable and easily-deployable solution that protects our data
What is our primary use case?
I use the solution for process control and issue management.
What is most valuable?
The product protects our data. The solution allows us to have both public and private repositories. The product is integrated with other solutions.
What needs improvement?
The solution could be more user-friendly. Sometimes, I feel lost while using the dashboard.
For how long have I used the solution?
I have been using the solution since 2016.
What do I think about the stability of the solution?
I rate the solution’s stability a nine out of ten.
What do I think about the scalability of the solution?
Less than ten people are using the product in our organization.
How was the initial setup?
The initial setup is not complex.
What about the implementation team?
The deployment can be done in-house. We need one administrator and one developer to maintain and deploy the solution.
What other advice do I have?
The product is mostly used by developers and DevOps teams. Bitbucket is more user-friendly than GitHub. If we have a GitHub account, we can invite users. People wanting to use the product should use the free version and understand the features well before buying the licensed version. Overall, I rate the solution a nine out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-05-22T00:00:00-04:00
Rated 5 out of
5 by
Sven Gotovac from
A simple and stable solution useful for tracking changes
What is our primary use case?
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.
What is most valuable?
It's a tool for collaboration, and that's what we use it for in our company.
What needs improvement?
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.
For how long have I used the solution?
I have experience with Git. Also, I don't remember the version of the solution I am using.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How was the initial setup?
I wasn't involved in the setup.
What other advice do I have?
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.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-07-07T00:00:00-04:00
Rated 5 out of
5 by
Rahul Rajpurohit from
Helps to store code in a single repository
What is our primary use case?
We use the tool to store codes.
What is most valuable?
Our team members can work together and save the code in a single repository.
What needs improvement?
The product needs to improve its UI.
For how long have I used the solution?
I am using the tool for four to five years.
What do I think about the stability of the solution?
The product is stable.
What do I think about the scalability of the solution?
My company has more than 1000 users for the solution.
How are customer service and support?
The software's technical support is good.
How would you rate customer service and support?
Positive
How was the initial setup?
The product's initial setup is easy.
What's my experience with pricing, setup cost, and licensing?
The tool is an open-source product.
What other advice do I have?
I would rate the product a ten out of ten.
Which deployment model are you using for this solution?
On-premises
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-04-26T00:00:00-04:00
Rated 5 out of
5 by
Vijaya Das from
A stable solution that can aid its users in maintaining all application developments
What is our primary use case?
Regarding the use cases of the solution, I use it for my version control, pipelines, data pipelines, reports, specifically BI reports, and for all the other processing-related things. Also, all the application developments which happen are maintained in Git.
What is most valuable?
For me, the most valuable feature of the solution is that I can compare the old or previous and the new version of Git.
What needs improvement?
The dashboard is the one thing that could be improved in Git. In our company, we sometimes feel the need to have certain kinds of reports, but we never get those customized reports in Git's dashboard.
For how long have I used the solution?
I have been using Git for five to six years. Also, I guess that I am using the solution's latest version.
What do I think about the stability of the solution?
So far, the product has been stable. Stability-wise, I rate the solution an eight to nine out of ten.
What do I think about the scalability of the solution?
Scalability is something I haven't experienced. So, a bigger team in my company looks after the scalability aspect of the solution. Therefore, I will not be the right person to rate it from a scalability perspective. Around 200 users are using Git in my company. I am not the right person to comment on whether the solution's usage rate will increase in the future.
How are customer service and support?
I have never contacted the technical support team, but my team might have. I don't get into the details my team manages since I work at a product management level.
How was the initial setup?
I was not involved in the setup process, but my team was involved in it. So, I think the setup process should be okay. However, I can say that its performance seems okay.
I don't know the deployment process since I wasn't involved in the deployment process.
What's my experience with pricing, setup cost, and licensing?
I don't know about the pricing details since I wasn't a part of the buying process of the solution.
What other advice do I have?
I would definitely recommend the solution to those planning to use it.
Overall, I rate the solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-04-26T00:00:00-04:00
Rated 5 out of
5 by
Simon Wanyutu from
User-friendly, easy to install, reliable, and effective project management
What is our primary use case?
I use Git to manage my personal projects involving web basics, web design, and web pages. I am able to clone most things using Git.
I use it for web design version control. I also conduct a lot of research on open-source technologies that we can install using Git.
I have discovered that most of the solutions offered on Git can also be found on Docker.
How has it helped my organization?
It would be preferable if the updates could be completed at a faster pace.
What is most valuable?
Version control is beneficial as it allows me to keep track of all the modifications I have made to the applications.
What needs improvement?
I have no problems with Git and prefer using the Terminal Point of View for its high speed.
I attempted to use an alternative user interface, but it was too sluggish for me. I discovered that the Terminal is more efficient and rapid for executing events on Linux and Ubuntu. Its swiftness in event deployment is remarkable.
For how long have I used the solution?
I have been working with Git for three or four years.
I update the versions every now and then.
What do I think about the stability of the solution?
I would rate the stability of Git a nine out of ten.
Performing periodic updates can be time-consuming, but it is not a significant concern as it doesn't disrupt my schedule. However, I do need to make a conscious effort to initiate the updates.
What do I think about the scalability of the solution?
Git is a scalable solution.
Another advantage is that any team can work on it effortlessly, even large teams, making it highly collaborative.
I am currently using it and there are only a few people who I would like to share my changes with. With the current capability to view the modifications I have made, I am able to open it and see the updates for my team.
I am not planning to increase my usage at this time.
How are customer service and support?
I have not contacted technical support.
Which solution did I use previously and why did I switch?
Ever since I began my training in web and development, it was the easiest platform for me to use and was the only one that was introduced. I did not explore others.
How was the initial setup?
The initial setup is straightforward.
The deployment process was quick for me. I was able to execute it on my personal computer and also clone it to my personal Git account.
What's my experience with pricing, setup cost, and licensing?
I am not required to pay due to the small number of users we have.
We have a small user base, and we are not using the enterprise version.
What other advice do I have?
I highly recommend others use Git for version control.
Because of its version control, I would rate Git a ten out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-04-24T00:00:00-04:00
Rated 5 out of
5 by
Jordan Borgner from
Well integrated, robust, quick and easy to install
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Git for two years. I use it occasionally.
I am working with the most recent version.
What do I think about the stability of the solution?
I would rate the stability of Git a ten out of ten.
What do I think about the scalability of the solution?
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.
How are customer service and support?
I don't believe they offer technical support.
Which solution did I use previously and why did I switch?
I have used Confluence and Jira from Atlassian.
How was the initial setup?
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.
What about the implementation team?
It can be deployed by anyone who is using it.
What's my experience with pricing, setup cost, and licensing?
Git is completely free.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-03-03T00:00:00-05:00
Rated 5 out of
5 by
JinyongKim from
Reliable and has high user popularity
What is our primary use case?
I am an engineer and I am using Git for research. I follow the event issues that can take place.
What is most valuable?
The most valuable feature of Git is its reliability and user popularity.
What needs improvement?
If the solution could provide more language support options such as Korean, it would be helpful.
For how long have I used the solution?
I have been using Git for approximately three years.
What do I think about the stability of the solution?
The stability of Git is good.
What do I think about the scalability of the solution?
We have approximately 500 users using this solution in my company.
How are customer service and support?
I have not used the technical support of the solution.
Which solution did I use previously and why did I switch?
I have not used similar solutions to Git.
How was the initial setup?
There is no installation for the solution because it is cloud-based.
What other advice do I have?
I would recommend this solution to others. It is popular.
I rate Git an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-03-25T00:00:00-04:00
Rated 5 out of
5 by
VenkateshK4 from
Straightforward setup but not 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.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-04-13T00:00:00-04:00
Rated 5 out of
5 by
YATIM Khalid from
Good distance access, stable, and scalable
What is our primary use case?
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.
What is most valuable?
The most valuable feature is having access to the local country repository even if we have problems with distance access.
What needs improvement?
The UI can be more user-friendly.
For how long have I used the solution?
I have been using the solution for two years.
What do I think about the stability of the solution?
I give the stability a ten out of ten.
What do I think about the scalability of the solution?
I give the scalability a nine out of ten.
We have thousands of users.
Which solution did I use previously and why did I switch?
We switched to Git because we had distance access issues with our previous solution.
What other advice do I have?
I give the solution an eight out of ten.
I recommend the solution to other users.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-03-10T00:00:00-05:00