GitHub Reviews

GitHub is an excellent platform for organizing all sorts of information. I personally found it beneficial for keeping track of my coding projects, and recommendations, and occasionally making commits. By creating branches, I could easily focus on specific areas and even delve into things like creating my website using GitHub pages. Overall, I found these features to be very practical and advantageous.

In my case, I prefer to keep my repositories public, especially for small-scale organizations that don't require a high level of privacy. I find it useful to maintain a public profile because it allows me to showcase my work whenever I'm looking for a new job or updating my profile. By doing so, others can visit my profile, review my details, and verify the accuracy of my work history. This way, I can confidently stand by everything that I have accomplished throughout my career.

The most valuable feature of GitHub is version control and continuous integration.

The solution can improve by adding video guides, official guides, or short courses that cater to beginners who are new to the system. These resources could offer step-by-step guidance on how to use GitHub, including common procedures such as pulling and committing. Currently, many of us have to resort to searching for information on how to do these tasks via Google. An official guide provided by GitHub itself would be a valuable asset to newcomers and would save them time and effort.

There is potential for GitHub to enhance its features to be more like a Jenkins pipeline or CI/CD pipeline. While I currently use GitHub for code integration, I would like to see more emphasis placed on code management and automation. It would be beneficial to have more input on these areas within GitHub.

I have been using GitHub for approximately five years.

The stability could improve.

I rate the stability of GitHub a seven out of ten.

We have approximately 20 software developers using this solution.

I rate the scalability of GitHub a seven out of ten.

The support could improve. I have received online discussion forum support but it could improve.

Neutral

We might be switching to GitLab.

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

I am using the free version of the solution. However, there are some costs my organization pays.

My advice would be to take some time to clean up your repository and organize your data, step by step, in order to optimize its performance and make it more user-friendly. It can be challenging to work with applications like this when there is a lack of resources or input. However, by investing time in making your repository more efficient, you can reduce the potential for overwhelm and streamline your workflow.

I rate GitHub a seven out of ten.

Our primary use is for open-source code management and distributed version control. We use the solution to coordinate the work of developers, assisting them in developing and maintaining our source code. We also use the tool for code review purposes using the GitHub repository, where I can comment on or review lines of code for developers to edit and improve performance. They then receive a notification alerting them of the desired update, which the project developer and project lead can approve.

The best feature is the ability to track the history of all code changes, and it's easy to use. Additionally, as it's open source, anyone can use that feature resulting in distributed development. This opens the door to collaboration with different code and developer, feature, and master branches of development.

The solution also features robust security, high speed, and good integrity.

Excellent code management means that, even when developers accidentally delete sections of code, it's easily retrievable. GitHub reduces developer workload and saves them time.

The GUI design is poor, so I exclusively use the CLI, which is much easier to use and understand. It would be great to see the GUI updated to be more user-friendly. 

It isn't possible to run different branches simultaneously, and it would be good to see support for that.

We have been using GitHub for over seven years. 

GitHub is very stable; we can use it throughout the development process.

The solution is highly scalable. We have between 100 and 150 end-users, both developers and testers.

We haven't encountered an issue we couldn't fix ourselves or by using Stack Overflow or Google, so good community support is available.

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.

GitHub is an open-source application. It's free to use.

I would rate the solution an eight out of ten. 

We use GitHub because it's open source and makes code management straightforward; it's simple to track different code versions and change history. It's an easy-to-use, efficient application.

For someone looking to use the solution for the first time, I would say it's straightforward and possible to learn the significant features in a day. Learning to clone projects, push and pull code, and use comments is simple.

I use GitHub to keep and maintain my code and have version control. I connect with GitHub through an application called GitHub Desktop.

GitHub's version control is valuable. A recent example was when I connected a website with GitHub, which I developed in my local environment on my computer. I kept updating the plugins directly from my computer, and then I deployed the code through GitHub, which reflected directly into the live website. GitHub sped up the development process, and I felt safe because if something went wrong, I could always go back to my previous code, so I wasn't worried I would break the whole website. It is good for developers because they have version control over their code.

Moreover, with GitHub, finding other people's code is easy. There are a lot of users who host their code on GitHub and open it to the public. Sometimes, you can learn from their code or just use their solution, so it's very good for the developer community.

GitHub is good for controlling and managing the code without destroying it.

It would be good if there were training materials for junior developers.

I've worked with GitHub for about three years.

GitHub is stable.

GitHub is scalable. It's just me using GitHub for my code. But if you had a bigger project with a team, you could always invite anyone to work with the code. GitHub is good for teams because everybody can start with one main code and then open their branch to code freely without destroying any other code. However, there should be one administrator who performs tests to combine each code.

I use the free version of GitHub.

Many big companies use GitHub, such as WooCommerce for example. There are a few ways to use GitHub, like through Terminal. I personally like to use GitHub Desktop because it makes it easier for the user. I rate GitHub a ten out of ten because it is very useful. I remember a time before GitHub when it was quite painful to be a developer. If I'd write code and then want to make an update, I would have to save everything in version one, then version two, and continue doing so for newer and newer versions. Then I'd end up wondering which one was the latest because it was so confusing. GitHub made it much easier to check my code and review it.

GitHub provides good time reduction and this is what I value the most. My team uses GitHub for working remotely. Security is also a good feature of the solution. It's as if the solution creates a security barrier in the server, whereby I can push changes they make to my server once they come to GitHub. 

The solution has a lot of features. Should my developer leave tomorrow, the changes he has made will remain, even as another developer could do the work.

The branches created for the separate software and enrollment should be improved. There is a need to create separate software branches, such as for the production, operation and development teams, who are licensed, in respect of their need to match to test what they develop in a test environment. I can immediately go back and look at the features to see if they are up to the mark, such as those involving unnecessary code. 

As someone who works in infrastructure, I know how hard it can be to create things on this level, but it can be worthwhile. Confirmations and requisite future updates are in the end user's domain. The migration of the databases, such as the migration of my websites to the new WordPress sites, works at times but is slow. In such a case, the hardware must be increased. When it comes to the question of whether we should change to new servers and set up a new infrastructure level, I have found GitHub to be very helpful. It pushes the code directly to the repository and dumps the database on the other end. 

The security point should be addressed in the next release. Scaling is also an issue. If the code is very high on the user side and I should suddenly find myself wanting to increase the monthly use of my website from 10,000 to 30,000 people, it can create an imbalance in the infrastructure. In the case of the code level, we may see issues involving optimization. 

I have been using GitHub for more than seven or eight months. 

The solution is easily scalable and encourages migration. While I have other products at hand, GitHub makes things fun. We wish to lead and expand. We want to scale this project to the next level, since we have certain customers in hand.

I had to make use of technical support two months back, when I first started working and had a learning curve. This was while I was exploring new ideas as relate to my infrastructure experience. When encountering changes to the core side or the scaling, it is necessary to make use of technical support. An abrupt increase can cause problems with the infrastructure, so I am looking for solutions that will not require me to make changes to it each time this should occur. GitHub allows the core to be scaled up with ease and it offers auto scaling. 

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.  

Our initial deployment was with Cloud One. The cPanel is the browser involved. We make use of WordPress.  

GitHub is the perfect tool for use at present and is extremely necessary. It is one of the best solutions out there. Apart from GitHub, you need to use the local Git version control system since it involves code on a cloud platform. Git version is very helpful. One could download the large types of codes to do on the core level so that there will not be a need to go to the cloud setup every time. The code commands can be run from the local system. Setup and migration can be done with ease. The person would set up the order and the view. In my experience, GitHub is very easy to operate. 

I rate GitHub as a perfect ten out of ten. 

I previously used different tools. At present, I am utilizing GitHub and providing assistance with cell phone numbers. The solution allows me to make workspaces and perform changes with ease. It also allows for easy monitoring. I receive updates from Slack for confirmation purposes. There is no need to wait on my developers, as a connection can be made with the production server. 

I use GitHub for development, including version control and container services.

With GitHub, we can manage our development progress, CID, and continuous integration. It helps streamline our development processes effectively.

I really like the functions that GitHub offers. The features are very helpful for my needs.

There could be some improvements related to the automation of certain processes, especially with the integration of artificial intelligence. This would make some tasks more efficient.

I have been working with GitHub for more than one year.

I would rate the stability of GitHub as nine out of ten. It is very stable for our needs.

For scalability, I would rate GitHub nine out of ten. It scales well with our requirements.

The setup process for GitHub was straightforward and not complex.

If you are a start-up or a small company with a few projects, GitHub could be expensive because of the management costs.

We use GitHub for developers' deployments and issue management. We follow a Scrum setup, utilizing boards, story-testing tasks, and epics for effective visualization.

GitHub has been very beneficial in visualizing our planning boards, handling big planning items such as epics, and helping us manage tasks and issues effectively.

The ease of the planning board feature in GitHub is very valuable. It allows us to work with different boards easily and effectively visualize big planning items, such as epics.

The query function in GitHub is a bit stiff. They should introduce a query function similar to Jira's JQL for writing complex, nested queries. It’s difficult to write complex queries in GitHub, introducing or, and, and if functionalities.

I have been working with GitHub for two years.

The overall stability of GitHub is high. I rate it an eight out of ten.

The scalability of GitHub is comparatively low. I would rate it a four out of ten.

We have not reached out for technical support, so I cannot rate the customer service.

We used Jira before moving to GitHub. Our trial license for Jira expired, and they did not support us with a free offer, but GitHub does offer free support.

The initial setup was a bit complex and confusing, especially since I was self-learning. It was challenging to understand where to do all the configurations.

We had skilled people familiar with GitHub who drove the implementation. We had a working environment up and running within three weeks and have been improving it continuously.

We moved to GitHub as it supports us for free. We are a tech-for-good organization.

We evaluated Jira before switching to GitHub.

GitHub's simplicity is valuable, but there are some limitations in fields and configurations that could be improved.

I'd rate the solution eight out of ten.

I use GitHub as a code repository, and we use GitHub Actions a lot to trigger our pipelines.

The most valuable features are GitHub Actions for triggering workflows, GitHub Secrets for saving credentials without needing a third-party service, and the UI for identifying errors in the code when we commit.

Regarding improvements, I preferred the tool's earlier pricing model, which limited storage and the number of repositories instead of the number of users, which was more convenient from a customer perspective. I've also experienced issues with GitHub servers being unable to support moving repositories, which caused problems. For basic plans, no support was available to help resolve these issues. I think GitHub should provide more support for smaller businesses to help with these problems.

I have been using the product for six to seven years. 

For stability, I'd give the solution a seven because we faced 500 server timeouts a couple of times under a heavy workload. It's a good product; otherwise, that was just one instance I could think of.

I recommend GitHub for small, medium, and large companies. However, for very large businesses spending a lot of money, there are other options with more functions and features.

I rate the product's scalability a nine out of ten. 

The community support for GitHub is good enough. However, the official support from GitHub itself is not the best.

The initial setup is quite straightforward. The UI is interactive, so I don't see any problems there. It should be fine with any issues. I'm using the cloud-based version of GitHub.

Regarding pricing, I'd rate it eight out of ten. It's decent and not too expensive, and small businesses can also afford it. With AWS taking CodeCommit out of the market, I don't see many competitors for small companies in terms of GitHub.

There are options like GitLab with more functions and features for very large-scale businesses that spend a lot of money.

I'd give GitHub a nine out of ten as a product and would definitely recommend it to other users.

We are using GitHub as a repository for a couple of customers to be able to do Infra as Code in Microsoft Azure for them.

The most valuable features of GitHub are the ease of integration into Microsoft Azure DevOps. The process that you need to deploy into Microsoft Azure becomes fairly simple and the templates are already available, a lot of the engineers find it easier to use.

GitHub could have better integration or capability with other solutions.

I have been using GitHub for approximately four years.

GitHub is highly stable. Our team has not had any trouble with it.

The scalability of GitHub is good. I have not come across any limit.

We have six people using this solution in my organization. We have plans to increase usage.

I have not used the support from GitHub.

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

We did the implementation in-house for GitHub.

 The licensing model from GitHub is very clear.

I recommend this solution to others. There may be some customers that are very picky about not having code on the cloud, and then my recommendation would normally be to use Microsoft Azure Repos, which is essentially a clone of GitHub but it stays within your subscription and within your tenancy on Microsoft Azure.

I rate GitHub a nine out of ten.