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.

We use the product for software development and version control. It helps us to maintain a safe repository of our development. 

Git offers the ability to roll back to the previous version. You can also track all the small changes that you do. 

The tool is complicated for a beginner. You need to have some training to use it. It is also hard to find a parameter. 

I have been working with the solution for seven years. 

The product is stable. 

There is no technical support since we use the open source version. We find support mainly on the forums. 

We use the open source version. 

I would rate the product an eight out of ten. The product is the best in the industry. 

Git is mainly used for code repository and version control.

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. 

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.

All of the features in Git are useful.

The solution could improve by having more customization.

I have been using Git for a few years.

The stability is good.

I rate the stability of Git a ten out of ten.

We have approximately 500 people using the solution.

The solution is scalable.

I have not used the support.

I have used solutions prior to Git.

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.

We did the implementation in-house. We have a team that handles the implementation.

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.

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. 

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. 

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.

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. 

I've been using the solution for more than five years now. 

The stability is okay. I'd rate it six to seven out of ten. 

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. 

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. 

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. 

It's not too complex to set up. The solution is simple to implement. It can differ from project to project. 

We mostly use the free version of the solution. We also use GitLab, which has a licensed version. 

I'm a Git user. 

I'd rate the solution seven 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.