Git offers branch management, version control, and automation to facilitate quick deployments and team collaboration. Supporting CLI and GUI, it integrates seamlessly with platforms like GitHub, providing a stable environment for code management and deployment.
| Product | Mindshare (%) |
|---|---|
| Git | 13.4% |
| Bitbucket | 12.8% |
| GitHub | 10.3% |
| Other | 63.5% |
| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| GitHub | 4.4 | 10.3% | 100% | 102 interviewsAdd to research |
| Bitbucket | 4.2 | 12.8% | 98% | 53 interviewsAdd to research |
| Company Size | Count |
|---|---|
| Small Business | 11 |
| Midsize Enterprise | 8 |
| Large Enterprise | 16 |
| Company Size | Count |
|---|---|
| Small Business | 79 |
| Midsize Enterprise | 20 |
| Large Enterprise | 72 |
Git's branch management, version control, and seamless integration with other platforms like GitHub make it a fundamental tool for software development. Its capabilities allow multiple users to work simultaneously, making it ideal for collaborative environments. Git is easy to learn and supports both command-line and graphical interfaces, providing flexibility in usage. It maintains a detailed log of modifications, assisting in efficient code tracking and troubleshooting. While its pricing model and merging capabilities could see improvements, as well as UI enhancements, Git still stands out for its reliability and performance.
What are Git's most valuable features?Git is employed extensively in software development for version control and collaborative coding. It's integral in web design and configuration management where maintaining multiple code versions offline is crucial. Organizations leverage Git for project and application development, benefiting IT departments and research activities with its robust repository management capabilities. Both cloud and on-premise deployments enhance productivity across industries.
| Author info | Rating | Review Summary |
|---|---|---|
| Sr PHP Developer at GE | 4.0 | We use Git for configuration management because it is easy to use and supports parallel working. Before Git, we used other solutions but switched for better stability. However, its user interface could use some improvement. |
| Director - Technical Product Management at Visa | 4.0 | I use Git for version control and various pipeline and application development tasks. Its most valuable feature is version comparison. However, the dashboard could be improved to support customized reports, which we sometimes require in our company. |
| Azure DevOps Lead at DXC Technology | 4.0 | I use Git to download code from GitHub, make changes independently, and push updates back. I appreciate its merging features but wish it could resolve conflicts on the same line automatically. A GUI like Visual Studio Code would be beneficial. |
| Scientist - Instrument II at AbbVie | 5.0 | We use this easy-to-learn, stable, and scalable open-source solution for hosting and developing software. Setup is easy, and support is good. We recommend adding tutorials for new users to optimize their experience. We rate it 10/10. |
| Lead Technical Instructor at Code.Hub | 5.0 | I find Git essential for software development. It's powerful and boosts productivity by promoting collaboration and efficient code organization. However, effective branch management is crucial to avoid confusion. Despite this, Git's benefits far outweigh any challenges, making it indispensable. |
| Senior ict specialist at Information& eGov Authority | 4.0 | I find Git easy to use, especially after exploring a few online tutorials. However, it would be beneficial if it included a feature for monitoring data recovery similar to Azure. |
| Senior Data Archirect at Yettel | 4.0 | We use Git to store and track software development versions, and plan to integrate it for ODI versioning. Although the implementation process is easy, the user interface could be more user-friendly. We've not considered other solutions or cloud providers. |
| Professor at FESB - Faculty of Electrical Engineering, Mechanical Engineering and Naval Architecture | 5.0 | I use Git primarily for downloading and tracking changes, as its collaborative features are beneficial for our company. However, frequent upgrades are problematic, as they often break functionality, requiring substantial time to fix, which disrupts our update schedule. |
| Senior Engineer at Apexon | 4.5 | I primarily use Git for code repository and version control due to its performance, stability, and availability. While the ROI is good, I suggest a better pricing model for individuals. We switched to Git from SVN for its cloud capabilities. |
| Systems engineer at Expleogroup | 4.0 | As a student and at work, I use Git for version control, finding it accessible via terminal or GUI. However, synchronization and the initial setup can be complex. Despite this, its ease and functionality make it valuable for storing code and documents. |
Git's user interface could be improved.
I have been using Git for almost eight years.
Git is a stable solution.
Git is a scalable solution. Around 2,000 users use the solution in our organization.
Before Git, we used other solutions. We switched to Git for better stability.
Git's initial setup is a bit complex and not easy.
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.
I would recommend Git to other users.
Overall, I rate Git an eight out of ten.
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.
For me, the most valuable feature of the solution is that I can compare the old or previous and the new version of Git.
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.
I have been using Git for five to six years. Also, I guess that I am using the solution's latest version.
So far, the product has been stable. Stability-wise, I rate the solution an eight to nine out of ten.
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.
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.
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.
I don't know about the pricing details since I wasn't a part of the buying process of the solution.
I would definitely recommend the solution to those planning to use it.
Overall, I rate the solution an eight out of ten.
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.
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.
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.
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.
We have been using Git for the last four or five years.
I rate Git seven out of 10 for stability.
I rate Git seven out of 10 for scalability.
I rate Git support seven out of 10.
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.
Git is an open-source solution.
I rate Git eight out of 10.
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.
The best thing about this solution is that it can be learned very quickly, and used very easily.
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.
We have been using this solution for more than three years.
We have found this to be a very stable solution.
This solution is easily scalable, and can comfortably handle multiple users accessing the system at the same time.
This solution provides a lot of support online, that gives quick access to fixes for the majority of issues.
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.
This is an open-source solution, so there are no licensing fees associated with it, and no extra, 'hidden' charges.
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.
The tool is integrated into our environment and transmits our data and code to the repository.
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.
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.
I have been using the product for five to six years.
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.
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.
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.
We did the deployment in-house.
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.
Git is an open-source software.
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.
It is a stable product.
It is a scalable product.
Git’s technical support services are satisfactory.
Git’s initial setup has 60% complexity. In the beginning, it was not easy to set up for us. Although, with more experience, it has become more accessible. It takes a few days to complete. We have to make sure we have covered all the essential things.
The platform is less expensive.
I rate the product an eight out of ten.
We use Git for storing software, development, and tracking versions. We have plans to use it for ODI as well, mainly to unify software version tracking. Although ODI already has its own internal versioning control, we can also transfer it to Git.
The implementation is easy.
The UI can be more user-friendly.
I have been using Git for around four years.
Git is stable.
I believe Git is scalable.
I give Git an eight out of ten.
We have a few hundred end users.
I recommend Git to others.
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.
It's a tool for collaboration, and that's what we use it for in our company.
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.
I have experience with Git. Also, I don't remember the version of the solution I am using.
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.
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.
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.
I wasn't involved in the setup.
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.
The performance and stability give you very good control. Definitely, its availability is another valuable feature.
There is room for improvement in the pricing model of Git. Maybe providing a cheaper version for individual users.
I have been using Git for twelve years. I am using the latest version of Git.
The stability of the solution is good. I would rate it a ten out of ten.
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.
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.
The ROI is good.
There are free versions available, but if required, you need to pay for licensing.
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.
I would definitely recommend using this solution.
Overall, I would rate the solution a nine out of ten.
As a student, I used Git to store my source code and versioning. Whenever I do modifications, I can roll back the session if needed. It's the same at work, but we use Git to store documents.
I like that it's easy to use and because it's accessible from a terminal or a graphical user interface if needed. I also like that we can pass comments from Linux if required.
Synchronization could be better. Sometimes when you create a branch and merge it into another branch, I think it's a bit complex for no reason. The initial setup is also tricky when you do it for the first time.
I have been using Git for almost ten years.
Git is a stable solution. I have never had a problem with this solution.
On a scale from one to ten, I would give Git a nine.
I think Git is scalable. We were always a team of five to ten members, but I think it can handle more. We are an engineering company, and half the company uses Git.
The initial setup is a bit complex if you're doing it for the first time. It also depends on what you're trying to do. If it's just to push code, it's straightforward. But when you have to manage a big project, it can get complicated. For example, you must get information from other branches after setting up your branch. When you merge data, you must ensure you do not touch all this information. Deployment time depends on the project and its scalability.
The deployment steps include creating an account, changing your key, synchronization with the project, creating your branch, and creating your own files and modifying them.
Other members of my team and I implemented this solution.
As a student, I didn't have to pay for the license.
I would tell potential users to read the tutorials and guidebook to understand Git and start doing things inside. You can quickly merge and create branches and versions. You have to be trained to use Git; then, it's easy.
On a scale from one to ten, I would give Git an eight.
