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.

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.

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

Git's initial setup is a bit complex and not easy.

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. 

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

I wasn't involved in the setup.

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.

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 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.

The product's initial setup is easy. 

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.

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

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

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.

The tool's setup is straightforward. I could complete the solution's deployment in two minutes. 

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.

The initial setup is straightforward. You initialize the repo in your code base, and you start committing changes.

It doesn't take very long to deploy it, a few seconds. It's a single connection.

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 initial setup was straightforward. The deployment took five minutes.

Git's setup is easy and I would rate it a nine out of ten. There are documents available with plenty of information. Hence, if there are any issues, you can sort them out. The tool's deployment is fast. 

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.

Git is easy to set up. I've done it multiple times on various systems, and it only takes a few minutes. 

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

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.

The initial setup is not complex.

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

Our technical team will be able to tell you exactly, but I believe they found some problems around the installation and so forth. I do know that it took them a while to actually get the automated deployment right before they could actually execute it. Perhaps the developers can make it easier in terms of getting readiness for automation deployment. It was quite complex and it took us about a day and a half. However, if you do a manual deployment, it doesn't take that long.

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. 

Git is not simple to set up.

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

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.