Git Reviews

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.

It would be preferable if the updates could be completed at a faster pace.

Version control is beneficial as it allows me to keep track of all the modifications I have made to the applications.

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.

I have been working with Git for three or four years.

I update the versions every now and then.

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.

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.

I have not contacted technical support.

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.

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.

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.

I highly recommend others use Git for version control.

Because of its version control, I would rate Git a ten out of ten.

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

The repository management and check-in/check-out commands are the most valuable features for ensuring secure code. It's a client-side tool that we install in our local company and connect to the cloud product for use cases.

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

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

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

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

The deployment can be done in-house. The deployment process is good but there may be a learning curve for some users. However, it could benefit from additional hands-on experience, particularly for enterprise-level usage.

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

The primary use case is to keep track of changes and maintain control, and it helps contain your code and is useful for collaboration.

One feature I find valuable is that it's a one-shot solution. Also, every software company has a requirement to use Git.

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.

I have been using this solution for ten years. We always use the latest version in our company.

It is a stable solution that has been fine for me for ten years.

I rate the stability a ten out of ten.

It is a scalable solution. Everyone can use it, and there are over 200 uses in my company.

The initial setup is a bit complex because it is open source.

We deployed it from some commands, which took just a few seconds. It's open source, so there is no need for a consultant.

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.

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.

We are using Git for development. We are cloning the code, pushing code, and raising pull requests. We use it for the typical Git workflow for development.

The solution has improved our company because I no longer have to copy the code on my own and keep it in a safe folder. This solution is organized and it's very useful in a team.

The most valuable feature of Git is the ease of tracking in time what the snapshot of the code was at a particular moment. The versioning is good.

Git could improve the merge conflicts. 

In a future release, the user interface should be easier to use and more intuitive.

I have been using Git for approximately three years.

Git is highly stable.

I have not used the support from Git.

I have not used a similar tool prior to Git.

There is only an online deployment of Git and it belongs to Microsoft.

We have received a return on investment using this solution.

There are some extra costs to Git, but it depends on your use case.

My advice to others is Git is the industry standard for source code versioning and my recommendation for them is to learn it and use it.

I rate Git a nine out of ten.

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.

You can have a central code repository using Git and have local code branches. 

I would like to see less updates with the product. 

I have been using the product for a couple of years. 

I rate Git's stability a ten out of ten. 

We Google the queries and look for support in communities. 

Git's deployment is straightforward. You need to run a few commands until you get a central repository. 

We can do the deployment ourselves. 

I rate Git a ten out of ten. 

Git is used to develop software.

Git's learning curve is shallow, making the solution easy to use after a few tutorials.

I would like more documentation.

I have been using Git for nine months.

Git is stable.

Git is scalable.

I am satisfied with the technical support.

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. 

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.

I use Git mainly to create new reports to store my project and to keep track of the changes I made in my code. So these are the main reasons why all people use Git.

I did use it in my organization as well. I did use it personally, but it was very easy to use it by yourself, especially when you create and upload your code, it's easy. If other people are included in their project, you're going to have to make merge requests to merge the code you made, and the code your colleagues have made. So it's a little bit complicated. So, when I started using it in my organization, It was a bit messy, but I finally got it.

Speaking about features, it helps to keep track of your code if it changes, especially to find who made the changes. The solution also makes it easy for other people to change your code.

I don't think it does need any improvement for now since Git is a free, open-source project.

To be honest, I didn't even get close to seeing all its current features. So, I can't imagine any new features that I would be able to recommend.

If it was possible to pay for a Git solution, I would pay for it. However, it's difficult in my country. So I mainly enjoy the free solution.

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

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

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

I never tried to reach tech support.

GitHub and GitLab were pretty good repositories for Git servers. So, I was using the solution on the cloud.

I did not deploy it. I was using already deployed solutions like GitLab and GitHub. I never did even try to deploy it.

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

My recommendation to others to use the solution would depend on their usage. If it's for their personal use, it's going to be easy. But if he was going to use it in an organization or for a personal project with a lot of friends or colleagues, then that would be a different story. You need to be concentrated, and I think a lot before making any changes to the code because every mistake can create a lot of problems.

I rate the overall solution a nine out of ten.

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.