Git Reviews

I use the solution for process control and issue management.

The product protects our data. The solution allows us to have both public and private repositories. The product is integrated with other solutions.

The solution could be more user-friendly. Sometimes, I feel lost while using the dashboard.

I have been using the solution since 2016.

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

Less than ten people are using the product in our organization.

The initial setup is not complex.

The deployment can be done in-house. We need one administrator and one developer to maintain and deploy the solution.

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.

I am an engineer and I am using Git for research. I follow the event issues that can take place.

The most valuable feature of Git is its reliability and user popularity.

If the solution could provide more language support options such as Korean, it would be helpful.

I have been using Git for approximately three years.

The stability of Git is good.

We have approximately 500 users using this solution in my company.

I have not used the technical support of the solution.

I have not used similar solutions to Git.

There is no installation for the solution because it is cloud-based.

I would recommend this solution to others. It is popular.

I rate Git an eight out of ten.

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.

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.

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

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

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.

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.

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.

Our primary use case is source control and code checking. We used it as version control for collaboration projects. The most important use case is being able to look into the code. Somebody can publish the code publicly in a standard format, which organizes the standard format of code. Then, the team follows the structure of the README file and the code structure.

I also used this solution to make my resume stand out.

What I find the most valuable about Git is that it is CLI and GUI-supported. People who do not like using the CLI mode can use the GUI mode. The solution also now comes with the VS (Visual Studio) code. The ID comes with the Git adapter. This is handy, that is why there is wide adoption of Git.

We have had a mixed reaction to the newly-introduced code pilot. It improved the coding but was also gave too much to the AI and people are concerned that Git Copilot could result in a lot of job losses.

I have been using Git for four years.

I would rate the stability of this solution a 10, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the scalability of this solution a 10, on a scale from one to 10, with one being the worst and 10 being the best.

Prior to Git, I used TortoiseSVN.

I would rate the initial setup process a four, on a scale from one to 10, with one being the most difficult and 10 being the easiest. The reason for this rating is that once there are conflicts, it takes a lot of effort to resolve them.

For the people looking to use this solution, I would say, go through some of the basic videos and learn the basic commands to get started and then explore more of the features. Get some hands-on experience and collaborate with others to find out more about the solution. 

Overall, I would rate Git a nine, on a scale from one to 10, with one being the worst and 10 being the best.

Git can be deployed on the cloud and on-premise.

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.

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.

I have been using Git for approximately five years.

Git is stable.

The scalability of Git is good.

We have only developed using this solution in my company.

I rate the support from Git a three out of five.

Neutral

We use another solution prior to Git.

Git is not simple to set up.

We did the implementation of Git in-house.

We did not evaluate other solutions.

We have one person that does the maintenance of the solution that accesses the cloud services.

I rate Git a ten out of ten.

We use this solution to assist with our development.

We are using the on-premise deployment model, with Git installed on our server.

The most valuable feature of this solution is the branch management functionality.

The GUI needs to be improved.

We have been using this solution for ten years.

The stability of this solution is very good.

For our use, scalability is not a problem.

We do not have a very complicated installation, with fifteen users. We do not plan to increase usage at the moment.

I have never used technical support, although support online is good. We have solved our technical issues by looking on the internet.

We did use another solution before this one but switched because Git was a better product.

The initial setup for this solution is complex. Specifically, it is difficult for the average user to configure. One person is enough to handle the maintenance.

We are using the open-source version, which is available free of charge.

We did not evaluate other options before choosing this one.

We are satisfied with this product, but updates to the interface would improve usability.

I would rate this solution a seven out of ten.