Git Reviews

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.

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.

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. 

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. 

The solution works perfectly fine so far. For the last year, it hasn't given me issues. 

I've been using the solution for one year. 

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. 

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. 

We primarily use GitHub. Now we are using Git for version control. 

The initial setup is very straightforward. It's not complex at all. 

You can pay for a subscription. It is an affordable product. 

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. 

I use Git for version control. It helps us to distribute development and manage source code. 

The tool's most valuable feature is branch workflows. 

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. 

I rate the solution's scalability a seven out of ten. My company has eight developers using it. 

I haven't contacted the tool's technical support. 

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.

I rate the tool's pricing a five out of ten. 

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. 

Git is easy to use. With the help of a few online tutorials, a person can understand how it works.

The platform could have a feature for monitoring data recovery similar to Azure.

We have been using Git for nine months.

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.

I use the solution for application development.

The product is easy to use.

The price could be improved.

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

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

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

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

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

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.

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

We use Git for the desktop to maintain some versions of the codebase.

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.

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.

I have been using Git for a year. Also, I don't remember the version of the solution I am using.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a ten out of ten.

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.

The organization looks into the pricing aspects of the solution.

I would recommend the solution to those planning to use it. I rate the overall tool a ten out of ten.

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.