We might be switching to GitLab.

I rate the initial setup of GitHub a seven out of ten.

I wasn't involved in the initial installation, but I installed the open-source flavor of Git, which was straightforward. Enabling the AD or LDAP is the most important thing in the enterprise setup. I have not looked into that because the customer enabled it. I never got a chance to integrate LDAP with the access management system within GitHub.

Setting up GitHub is extremely simple. You create an account in five minutes and have your first repository set up in another two after that. You're up and going in under 10 minutes.

It's a lightweight solution. The only maintenance is usually related to active stuff that we're doing on the platform. I wouldn't classify that as maintenance. That's product improvement.

The initial setup is mostly straightforward. The deployment takes one hour. 

The solution is cloud-based. I do not have to deploy it.

The initial setup is very straightforward; creating a repository and the paths required for local and other branches is easy.

The deployment time depends on the project size. We follow an agile sprint cycle so we can carry out new deployments every one to two weeks, and they don't take much time at all.

The initial setup of GitHub is simple. The full implementation took approximately a few hours. There was some user configuration that took some time.

I just manage the team. I've not involved in the more technical details. I wasn't present for the implementation process. I can't speak to how easy it was, or how difficult, via any first-hand knowledge. 

There isn’t really an initial setup to deal with.

There is a certain amount of difficulty involved in the work we did with the developer. This is because we use private repositories, not public ones, for security reasons and this requires the developer to have a code for a secure shell. 

When we do the initial setup in the cPanel, we are supposed to utilize it for our infrastructure. The enrollment is set up to the cloud and the cPanel and GitHub to the local systems, wherever the developer may be found. Usually, they are remote. We have confidence that the developer reposits first to his local system and from there to the cloud and we must execute shell for these development purposes.  

Regarding the initial setup, I rate it an eight on a scale of one to ten, where one is difficult and ten is easy.

The solution is deployed on a private cloud since it is a corporate thing. We don't go for a public cloud.

The deployment is fast since we just have to run the script, and once it's done, it takes a few minutes.

No installation is required.

The initial setup was very easy.

The setup was very straightforward and easy for me.

The setup of GitHub is very simple if you have a knowledge of Linux and follow the process document. 

The initial setup is simple and straightforward. it is not overly complex or difficult. 

As it is a solution that is on the cloud, there is no manual maintenance required. 

The initial setup is super easy.

The initial setup is okay. You need to know what you're doing.

There's no installation. However, you'll need other tools to help you with pushing the code to GitHub. Once you create your account and log in, it gives you the steps you are meant to follow, so that's good. It helps a complete beginner get started. They'd never get stuck.

The initial setup is a little complex because it requires some knowledge of GitHub and code versioning. Certain steps need to be taken in a specific order, and if any are skipped or done wrong, it can lead to failure. Aside from the mentioned challenges, one staff member can complete the setup.

There is sufficient documentation to help with the setup process.

The initial setup is straightforward and easy. For someone who has actually good experience in software development, including using a repository solution, I think it is easy. Beginners need to refer to the manual and see some online tutorials to receive assistance so that it is easier for them to setup.

The initial setup was very simple.  

It really depends on the application we're working on. I've seen deployments take as little as 15 or 20 minutes to push out a code change, up to hours or days depending on the functions that we're changing.

The installation for this solution is very easy. 

It's a simple process.

The initial setup is quite simple. It took less than an hour and could even be done in as little as 15 minutes.

It’s very straightforward to set up. It’s not complex at all.

The learning curve for GitHub is pretty small. The more advanced commands will take a bit of time to learn. However, the basic commands are easy to learn. In a few days, you're good to go.

It is pretty straightforward. You just use your login ID and credentials.

The initial setup for this solution was very straightforward.

The initial setup was straightforward. We are in a regulated industry with a large volume of organizations, and there are additional processes that need to be taken care of. Taking all that into account, the deployment took about 10 days. Implementation of GitHub alone just takes a few hours. We worked with a third-party vendor. 

There was no need for an initial setup as I just use the solution on the cloud. 

GitHub doesn't require any setup. You only need to create an account and a repository. After that, you start adding your files. 

My organization installed everything, including the two-factor authentication security. 

The initial setup is straightforward and only involved four to five steps. 

There's no installation process. 

The initial setup is straightforward.

The solution’s initial setup is straightforward.

In terms of the setup, only the clients have you install it on your side. You have some clients that used to access it from the desktop basically, so that is the only place where you have to install the solution.

It's cloud, so you don't need staff for maintenance. It's designing the branches only that you need to worry about. It's like Gmail. You don't need any people for maintaining it.

The initial setup is straightforward.

Client setup takes about 15 to 15 minutes on the workstation where I do my development.

This solution does not require a big installation. It can be used as and when it is needed without a huge commitment.

I did not really work on the deployment per see. However, it is really easy to create new branches. There are also great opportunities for integration with other tools, for example. There's some great automation, for example, which is helpful.

The initial setup of GitHub is very simple.

The initial deployment was straightforward and took three to four months.

Initial setup was very simple.

The initial setup was straightforward.

Its initial setup is straightforward and easy. It is much easier and simpler than Azure DevOps. This is something that Microsoft has to aim for.

I have experience in many tools. GitHub is not the hardest, and it is also not the easiest. It is of medium level.

The tool's setup is straightforward and takes seven days to complete. 

The initial setup was easy.

The initial setup was straightforward. 

There's no real setup required, we just installed it and hooked it up to our project, and we put it into the Docker file. Not much setup.

The initial setup is very easy and there are multiple ways to integrate GitHub Dash or to command prompt and that simplifies things. We migrated to pipeline to build and deploy the process. 

The initial setup was okay. It is not really difficult from my perspective.

It is so easy. It took about five minutes maximum. It was really easy to configure. But, as I told you, I couldn't figure out how I can use it with my local IDE or development IDE like VSCode or something like that. That's why I'm using Jira. If I use Jira I couldn't change the issue from GitHub to task. In GitHub I found it to be difficult with this.