GitHub Reviews

I use GitHub just for remote repositories, backup, and version control. I also use local Git.

GitHub hasn't affected my productivity too much. It's more for version control, releasing updates, and managing my work. It has made managing projects easier.

GitHub is very straightforward. I really appreciate the versioning capabilities, ease of use, and the ability to host code.

The integration with Visual Studio Code could be more streamlined, as it is somewhat convoluted at times. However, it is certainly easier than using the command line.

I have been using GitHub for probably three years.

GitHub is very stable. I have never had issues with too many bugs, nor has it broken down.

Scalability hasn't really been a concern for me with GitHub. I don't have to worry about scaling to more users; it's pretty straightforward.

I have never had to contact the GitHub support team. Therefore, I cannot comment on their customer service.

Positive

Setting up GitHub takes maybe five to ten minutes.

I find GitHub's pricing quite affordable. Although I haven't used a subscription model, the subscriptions seem very reasonable and are comparable to competitors' rates such as Bitbucket.

I would suggest being familiar with Git to fully utilize GitHub to its best benefit.

I would rate it a nine out of ten.

I mostly use GitHub to save repositories that I encounter when scrolling or searching for resources. Even if they are not immediately relevant to me, I know they will be useful in the future. So, I save those repositories in my GitHub account. Whenever there is any requirement from a client or a project with a similar base, I use those repositories for the data.

GitHub has made handling repositories more manageable and helps in organizing resources effectively.

The most valuable features are the speed, low latency, and the clear, concise set of commands. GitHub is not complicated to use and is very user-friendly. It's also beginner-friendly, making it welcoming for newcomers.

There is nothing that I find that needs improvement in GitHub. The introduction of GitHub Copilot has made everything much easier and flexible.

I have been using GitHub for around two years.

GitHub is a stable product. There are no issues with stability.

I have never needed to contact GitHub's support team. I have always found alternative solutions if I encountered any issues.

Positive

If you do not have any dependencies installed and you are starting from scratch, it takes about 20 to 25 minutes to ensure everything is according to your needs. While installing other dependencies and tools, GitHub can also be installed, so it does not require extra time.

The pricing is reasonable and not expensive.

I would recommend GitHub to others as it is user-friendly and easy for beginners to adapt to and learn. The introduction of GitHub Copilot has further simplified usage.

I'd rate the solution nine out of ten.

I use GitHub for version controlling of the code. I have experience using GitHub to upload the source code and manage tasks.

GitHub has improved efficiency by being easy to use for any user, and it offers good documentation that makes it easy to follow the steps.

GitHub provides enough storage for uploading the source code. It makes it easy to push code, and the Git commands are straightforward to use. The documentation is also good, and I appreciate the CI/CD pipelines that we use for web applications to upload the application in development mode and production mode.

When I was new, I faced challenges with Git commands, such as reversing or deleting mistakes. Additionally, merging code from multiple branches can sometimes result in conflicts, which are difficult to resolve.

I have been using GitHub for five years.

I have not faced any issues with the stability of GitHub.

For large-scale projects, there can be issues when multiple employees work on the same project and need to merge code into a single branch, resulting in potential conflicts. However, it's a problem with team understanding, not GitHub itself.

GitHub's support team is really good.

Positive

I used GetStream.io earlier, but I have not implemented it in a live application.

I do not know anything about the pricing.

I would recommend GitHub to my colleagues.

I'd rate the solution ten out of ten.

I use GitHub and the products from its integration partners, which include SOAR platforms, ServiceNow integrations, IBM integrations, Splunk integrations, and much more.

I use the solution in my company for code management and platform management purposes.

GitHub's features are more in a module and package format. It is always good to keep your repositories in one place so that other people or your team members can access them. If people leave and some new team members join the company, then they can be trained to use the product.

As a customer, I feel that there are certain gray areas associated with technical support where improvements are required. The support team needs to have a well-defined SLA model since it is an area where the tool currently has some shortcomings. The tool's support team is responsive. I get responses from the tool's support team whenever I ask them any questions. The ability to let users manage the SLA system can be an area that needs to be updated in the product.

I have fourteen years of experience with GitHub. My company has a partnership with GitHub.

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

Though I currently don't face any issues related to scalability, there are a lot of areas in GitHub where support is required. The current workforce dealing with the product is smart. In the current era, it is possible to get all the information through different sites, apps, mobile devices, and even YouTube. Rather than raising a support request with GitHub, the new workforce goes through the product's user manual and YouTube to find a fix to their problems.

In my previous organization, there were around 1,500,000 to 1,600,000 employees who used to use the product.

I rate the technical support an eight and a half out of ten.

Positive

The product's initial setup phase is easy but it is always good to connect with GitHub's team that manages APIs. If you are paying for the solution, you have the right to get support from the consultant because they bill you for one hour of availability irrespective of the platform's costs.

During the initial days of usage, there won't be any cost savings possible with GitHub. Once more people start using the product in your company, then you will start to experience the cost saving benefits from the tool.

If I consider the market standards, the product's price is pocket-friendly.

With fourteen years of experience with the product, I don't think I would face any challenges with it. For new users, it would be good if they could gather a detailed overview to understand the solution, and they could get information from YouTube or other social media platforms. I suggest that new users learn how to manage the product's setup phase. It is better to indulge in some self-study and do the homework, and parallelly consider using the support system offered by GitHub to learn about the product.

I have an experience with one of the Big Four companies, EY, where GitHub is used frequently.

I have already recommended the product to multiple clients, including PepsiCo, Kellog, Procter & Gamble, Bank of America, and Citibank. Sometimes, you have to manage all your codes locally, but it would be great to have everything managed on the cloud. As my company has been managing codes with GitHub for a long time, I always practice with the tool and get trained to figure out good ways in which certain things can be done with the product. I feel that there is a need to encourage people to use the product, and it can be a healthy thing since it will be possible for people in an organization to delete the local file once someone leaves the company, and it can be done at a global level.

My company plans to start the AI development project in one of the upcoming quarters. GitHub is the technical platform from which we cannot expect more, but we can race a request with the support team and tell them about our company's expectations and inform them that we need their help to deal with the AI model in the solution. If my organization plans to use the AI part, I cannot force GitHub to help me, but I will check to the extent to which I can receive help from the tool's support team. If I am developing some new model with the help of AI, then it is my responsibility to bridge the gap by considering factors at a solution level. I believe in always going for an approach involving a handshake with the technology partners and service partners.

During the initial days of usage, there won't be any cost savings possible with GitHub.

I rate the solution a nine and a half out of ten.

One major disadvantage, which I believe GitHub is and which the tool should work on, is that it does not provide good reporting capabilities from a compliance perspective. If we are using GitHub for 500 users, sometimes the compliance team asks for a certain kind of report on how many users are not active and who left the company, and GitHub does not provide such a granular report. GitHub should improve its reporting capability.

GitHub should work on enhancing its search capability. The tool should add some more features and functionalities.

I have been using GitHub for six to seven years.

Performance-wise, if we have set it up properly, we will not encounter any major performance issues with the tool. It works fine.

My company has an enterprise-level setup, so we have a large user base.

The technical support of the solution is good, and our company has used it for GitHub upgrades. We raised our tickets with the support team. Support-wise, GitHub is good. They respond back on time and give us the exact SOP, which we need to follow when we run into some specific issue where we need their support. Support-wise, they are good. I rate the technical support an eight out of ten.

Positive

Some other teams in my company use GitHub Actions.

The product's initial setup phase is straightforward. It is not very difficult. In our company, we have a setup on the server and on AWS also. We are using the cloud version of GitHub.

The tool's pricing was compatible with our company's needs. As far as other tools are concerned, I think, in terms of price, GitHub is okay compared to other tools.

Before GitHub, we used Perforce and some other products as source code management tools. GitHub is more agile-centric and flexible than other tools. GitHub is better accepted as a source code management tool, and that is the reason we are also using it in our company.

My company started to use GitHub as it is well-integrated with other tools and as it provides better support. Suppose you go into some issue or something like that. GitHub's support structure is better, allowing you to do more hit-and-test on the solutions than other tools. With GitHub as a tool, if you run into some issues, you get a lot of articles over the internet. Support-wise, GitHub is a better tool.

GitHub provides you with code-scanning capabilities. If we are using GitHub for CI/CD, it does provide such capabilities. From the code review point, it provides us with a feature to protect our branches and all that. It provides us the feature to help decide who can push to the repository or how many levels of reviews are required. I think these tools should work more on branching. In the branching area, the tool should provide a bit more flexibility.

My company has a couple of AI-driven projects managed with the tool.

The tool is not difficult to maintain.

GitHub is more development-centric and agile-centric, and it integrates with all our CI/CD tools and other things. The tool helps across the project teams to get things automated, and it helps in the quality review process, so eventually, it helps in quality delivery.

.

If some organization wants to go ahead with GitHub, there are definitely no cons or anything for which you will say that business units or companies would not go ahead with it.

I rate the tool an eight out of ten.

I mainly use it as a repository for source code. I worked on a project where the tool was also used for the CI/CD pipeline, but I didn't set up the pipelines, so for the whole test case, I just participated in the project.

The solution's most valuable feature is the reverse control system. The tool also helps organize collaboration by allowing users to share a repository with other developers.

Speaking of what can be made better in a solution is a difficult topic to discuss because it is not just technology. The tool could improve in the area of artificial intelligence methods. Recently, I made an error when I recently worked on a project since I was confused with some things, and it took quite some work to get it fixed again. Some kind of support in the area of merging should be considered for improvement. At the moment, any improvements in the aforementioned area would be something that I would appreciate as a user.

Specifically, I want the solution to offer AI-based merging support, as it is the only area where the product has certain shortcomings.

I have been using GitHub for four years.

The stability offered by the product is perfect, especially if I consider the use cases for which the solution is used in my company.

The scalability of the product is very good. Scalability-wise, I rate the solution a ten out of ten.

Currently, I am looking for a new project for my company. I know that in one of the last projects in our company, the tool was used by around 20 people. In the whole company, it was certainly used by more than 100 people.

In the past, my company has worked with SVN. I think now the standards are mainly GitHub and GitLab.

I would not be able to say the return on investment from the use of the solutions since there was no basic investment involved in the purchase of the product. The solution was available for free.

There are several licensing models available for the product. The basic licensing model is free, and if you need to have technical support and such things, then it does cost something. You only need to pay extra if you need technical support.

Speaking about a functionality of the product that was helpful, I would say that the product offers the capability of testing pipelines, but I don't exactly know what it did. I just knew that we use the testing pipeline feature in projects. The tool offers continuous testing, continuous development, and continuous deployment options that are useful in big projects.

Speaking about how the solution supported our team's collaboration across different locations, I would say that it helped my company with the fat git repository or code repository and also the repository of APIs.

I recommend the product to those who plan to use it.

GitHub is just one of the standard working tools for collaboration in the area of software development.

The product works well for developing environments by developers. The product was able to streamline some of the development processes in our company and also helped to increase the efficiency of the users, especially when compared to the old systems like Sentinel.

I rate the tool a nine out of ten.

GitHub is used to maintain code in a centralized place, which allows multiple teams to work on the same repository. It is also integrated with Jira and other tools like CACD pipelines. GitHub streamlines project collaboration by enabling developers to clone, modify, and push changes into a centralized repo. It supports project collaboration for software development processes.

GitHub aids in distributing work among team members, allowing them to focus on their own tasks without worrying about conflicts. By integrating with Jira, it helps track the progress of tasks and their states, such as development, merge, or deployment. It provides a secure and reliable way to store business code.

The most valuable features of GitHub include its ability to integrate with Jira and multiple CI/CD platforms like Techton, allowing for seamless project management. Additionally, the pull request feature, which controls code insertion into branches by code owners, is highly beneficial.

GitHub could improve in resolving conflicts when multiple developers modify the same line of code. Introducing a feature to manage and resolve conflicts directly within the application rather than on local machines would be beneficial.

I have been using GitHub for four years.

GitHub is stable, as I have never encountered or heard of issues such as application crashes or data loss. Even if server issues occur, GitHub takes responsibility, ensuring stability.

As an intermediate-level user, I find GitHub's scalability to be high, rating it at nine out of ten. Its advanced features allow maintaining multiple projects effectively.

I don't have any experience with technical support for GitHub.

Positive

Previously, I used GitLab, which has its own pipeline features. GitHub was chosen for its maturity, reliability, and global adoption by many organizations for application development.

GitHub is easy to set up, rated ten out of ten. Users just need to set up a username, password, and create an access token. It is user-friendly even with basic knowledge, and the GitHub official page offers simple documentation.

Each individual is responsible for maintaining their repository. GitHub management and maintenance are handled by all project team members collectively.

I have not paid for GitHub as I use the free version for personal projects. Organizations may take separate servers from GitHub based on their needs, yet I am unaware of the pricing details.

Users can trust GitHub as a secure place to store their business code because many large organizations use it. It provides a reliable centralized location for maintaining repositories, and its maturity and research make it a best-in-class option.

I'd rate the solution ten out of ten.

We have more than 100 teams in our organization using GitHub because it is a centralized repository tool. We have many interdependent applications, and GitHub provides a platform where people can share their codes in a particular directory.

GitHub's merging feature is much better than that of other products because merging is done daily. The solution's centralized administration is also very good, allowing you to onboard more than 200 or 1,000 people daily.

The solution's cost is high and should be reduced. Our company has a bundle product. Sometimes, people from outside our organization also need to collaborate with our code, and we need to integrate them as well. This causes problems for us because we also need to buy a subscription for them.

I have been using GitHub for two years.

I rate the solution an eight out of ten for stability.

I rate GitHub’s scalability a nine out of ten.

The solution’s technical support is very good.

The solution’s initial setup is easy.

We took help from GitHub's support team to deploy the solution. The initial setup is not very big, but onboarding people takes time. My company has more than 20,000 users. The solution's initial setup takes around one or two days.

We pay a subscription-based yearly licensing fee for the solution. If you buy extra support, you pay an additional cost.

The solution's deployment and maintenance is very straightforward. It does not take many people to deploy the solution. The planning part is very important. If you are planning for a big team, you have to plan very well. Planning the initial architecture is very important, and it can be done by an architecture team of one to five people. GitHub is far better than other products because it has a very good backend team.

Since we use a cloud version, it helps support our team's collaboration across different locations. An organization that has a lot of documentation should utilize GitHub. Otherwise, they will lose their data. GitHub is the main product in any software development organization. AI is only for data, but processing the data from AI needs to be stored somewhere. AI requires collaborating with other tools like GitHub, a repository tool.

Overall, I rate the solution an eight out of ten.