GitHub Reviews

We use the solution to handle our switch control. All our first code force is managed by GitHub to commit new features and create different branches. We even use this to manage the code to handle flows and processes. We can use it to create some branches and manage the code ownership, and we have an account for each developer so that they can submit pieces to code review for the user. 

The way we can manage the system is very useful. It'd great for managing code. 

You can have the main branch, and then create another branch, and easily merge them together if you like. 

You can effectively manage code reviews by issuing pull requests. Fellow developers can review my code, which helps ensure that the code is written correctly and clean. It's a useful exchange of information. 

The flow process helps us keep our applications stable. The released version is always running smoothly.

Once you get familiar with the system, it's very easy to use.

The product has a very user-friendly interface and user-friendly security.

There is a bit of a learning curve. At first, you'll have to do some searching online to figure out how to perform or reverse certain actions. When we have new team members, they tend to send you a full request for issues and it can create a bit of a bottleneck. There can be a lot of research and lots of problems initially created by users that don't yet understand the system.

The solution could use even more integration with automation tools. 

I've been using the solution for a while.

The stability is quite good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

There are four teams working with GitHub currently in our company.

I haven't had the chance to contact support, and therefore cannot really comment on how helpful or responsive they are. 

Within the company, we have specialized people who are maintaining the server. From my own experience as a software developer, outside the company, using the public community GitHub has on offer and publishing questions to it allows s to find the answers we need. The community is really responsive to us.

Initially, when I first joined the company, they were using another solution, and recently we decided to move to GitHub. We are currently using it on a daily basis.

There are other solutions that we use for source control and they're going to be migrating to GitHub.

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.

I personally use the free version. the company has the enterprise version of the solution. I'm not a part of the licensing process internally and therefore do not have details in regards to how much the company pays to use the enterprise version,

We are just customers and end-users.

We are using the latest version of the solution. We have some internal solutions deployed. We have our own private server, a GitHub server, and it always is properly maintained and always updated with the latest version for better performance.

I would recommend the solution, however, I would suggest those who intend to use it get the proper training on it first.

I would rate the solution at a nine out of ten.

It's mostly for versioning only, maintaining code branches, and sharing the code across to the wider community. It depends if it's a private one or a public one. It's mostly for collaboration across people.

There was versioning software before. It's now on the cloud and it's kind of available from anywhere, et cetera. You can access it from anywhere, and if you want, you can collaborate with a wider audience if you make a public repository. Otherwise, whatever was existing in versioning software, probably that's taken to the web and to the cloud to scale. 

The differences that they give upfront are good. You can evaluate and check whatever is being shared.

It's stable.

The solution can scale. 

We find it user-friendly.

Mostly they have the features that we need and they are currently being used. There are two approvals already. However, if something has to be moved into approvals, and if they don't approve it in a few hours, then they should move the approval request to some other user, or they should have a way to escalate it.

I've used the solution for only a year now. 

The solution is stable. There are no bugs or glitches and it doesn't crash or freeze. It has been reliable and the performance is good. 

We mostly use the solution for client projects. Across the company, I can't answer how many people use it exactly. We work with customers, so we see it used at the customer end.

We have not experienced any limitations of assets in terms of storage so far.

It's very scalable.

I've never used technical support for GitHub. I can't say if they would be responsive or helpful. 

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.

I don't handle the licensing. I'm not sure how it works or how much it costs. 

I'd recommend the solution to others.

I'd rate it, overall, at an eight out of ten.

Because Github is hosted in the cloud, we do not require many resources to maintain it. 

The security for this solution could be tightened up and improved. 

We have used this solution for three years. 

This is a stable solution. 

This is a scalable solution. 

We have not needed to contact their support team frequently. 

The initial setup was straightforward. 

The licensing offered is on an annual basis. 

During our use of GitHub, we have not encountered any problems and GitHub adds new features frequently. How useful these features are, depends on each business. 

I would rate this solution an eight out of ten. 

We are mainly using it for product development. Our repo and code are in GitHub.

It is a cloud-based solution. It is a part of our subscription in the cloud, and we have its latest version.

It has a lot of features from the code development perspective. You get a lot of features such as repo, commit, merge, and branch. You can play around and do things on the fly.

It is easy and simple to deploy. It is also easier to use when working from home.

It is currently only from the development perspective. It doesn't have features related to project management and testing. It is not like Azure DevOps. So, there is a lot of room for improvement.

It is a version control product, and it would be good if they can come up with a complete DevOps product.

Its stability is good.

Because it is cloud-based, you don't have scalability-related issues. We have around 30 users.

We didn't have to contact them because it is very user-friendly and easy to use. For any help, you can go to the communities.

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.

It is open-source. There is no license for GitHub.

If you are a startup or have a small team, it is a good platform to start with because you can achieve your business goal without any cost. It provides a lot of flexibility, and you can structure yourself for any kind of product development.

I would rate GitHub a nine out of ten.

Syed:
So, basically, I can store my code in some repository, so we can manage also that version control. So, if he developed some applications, so we can manage with versions, so that feature GitHub provide, so we can create some repositories. Through repositories, we can manage the versions, so it's very useful. So, also and that GitHub provide some CI/CD pipeline feature, so we can integrate CI/CD through GitHub, so whenever I commit that code, it will automatically deployed in our servers, so it was a very useful feature in GitHub.

Tutorial videos within the GitHub dashboard will very helpful.

I have been using this solution for one year. 

This is a stable solution. 

This is a scalable solution. We have between 300 to 400 users. There are five DevOps staff in our team who take care of maintenance.

This is an open source solution and does not include licensing. 

I would rate this solution a nine out of ten. 

My primary use case for GitHub is for my private projects that I'm developing for my customers. Some customers have their own developers and I sometimes support them to achieve their goals. So we share everything. We're also using GitHub for the documentation for the teams. I also give lectures for the organizations because sometimes they have development teams but they are not qualified enough, so I have to give them some training on it.

The features that I have found most valuable are that it can support you for most of the road map and it can automate some tasks which works really well with collaboration with the teams. They are really interested in how they organize the history of the code itself which is good.

In terms of what could be improved, I would say the security. I didn't try the two-factor authentication so I don't know if they have it already or not.

I sometimes found it very difficult to connect it with other tools, such as Jenkins or others. For the testing for example, I have to go between both sides. I don't know if I am using it right, but I don't know if they have these features or not. So I have to find other tools to support it because I couldn't really rely on GitHub for the steps that I needed.

Additionally, we are facing really big issues with the Arabic language in GitHub and I don't know if they are focusing on some improvement in the language capabilities. This is one of the things we're facing. 

As I mentioned, for the management we need some improvement in GitHub. It's not built for that. We really need some improvement for the project. It made it tough.

But overall I didn't find anything really urgent needed to improve.

I have been using GitHub for about eight years now.

I'm always using the latest update. In my service behavior I always update all the solutions.

GitHub is very stable.

Since I am working as a contractor in our organization and I'm doing the development work as a site project manager, I don't have a fixed team. But we can say that for each project it's about 10 to 20 people using GitHub most of the time.

It is used on a daily basis.

It is easy to add new users.

I was previously using Jira and Bitbucket but now I'm 100% in GitHub. I switched because of my team - they didn't work on Bitbucket. This is the reason I left Bitbucket even though GitHub is more costly.

I was looking for a management tool. Of course, Jira is the first try. When I looked at it for the cloud there were two options - GitHub and Bitbucket. But when comparing Jira's license to the licenses for Bitbucket or comparing the price between Bitbucket and GitHub, I found it's really cheaper for me to have Bitbucket. But because my team was most familiar with GitHub I decided I had to go with it.

The project management sector really needs some improvement for GitHub. I don't know if GitHub made sense for me as a project manager. But for what it was, it's a really good tool.

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.

I did the installation myself.

My recommendation for anyone thinking about GitHub is that it is the best solution - except for the price.

On a scale of one to ten, I would give GitHub a nine.

We use GitHub as a repository. 

GitHub needs to improve its UI. 

I have been using the solution for four years. 

GitHub is very stable. 

The tool is scalable, and we can leverage our DevOps projects using it. My company has 200 users. 

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

I rate the product a seven out of ten. 

We use this solution for completing repository services code on Azure. We use it for different customers and to design and test environments. We also use it for some background testing.

We are satisfied with the performance, and we've never had any performance issues because we generally use it on a smaller scale. Using the solution feels like we are running a massive development team comprising a couple of other employees and me. We design the environment and can manage the branching and design better.

There could be more integration into Azure. It will make it easier for us to present it to customers.

We have been using this solution for about three years.

It is stable, and we've never had issues.

It is on cloud, so it is pretty scalable. We use it in the consultancy department to test and see customer environments and errors. It is also good when doing a cause analysis because you can see the code that is being used.

The initial setup was easy.

It is a free solution.

I rate this solution a seven out of ten. I would recommend GitHub, but Visual Studio is arguably a bit better.