GitHub Reviews

I use GitHub for maintaining repositories, as it is easy to maintain freelance projects and to store college projects. I will be using it for hosting by providing a GitHub link.

For one of my freelance projects, I push the code or codebase to GitHub. From that repository, I get a link that I will host in Vercel or a Netlify platform. Then I will be able to get a public URL. That is how it is useful for me for freelance projects and college projects.

The feature I use the most is the GitHub clone feature because there are many repositories for study purposes, such as a portfolio or a Python-related project. I can easily clone the projects, open them in my window, and be able to work on them. That is the best feature I would recommend.

GitHub offers more options, such as more pro versions and more offers for GitHub Education, which I recently availed. The thing I wanted to add is the ease of maintaining repositories, and that is how it helps. It is a time-saving method because instead of having a manual method of hosting, I just push to GitHub, have the repositories, and then I am able to commit the changes easily.

The best features I will recommend are Copilot, then maintaining repositories is easier, then committing new updates, and the main feature is clone. I can easily clone GitHub repositories and open them on any other devices.

The feature I use the most is the GitHub clone feature because there are many repositories for study purposes, such as a portfolio or a Python-related project. I can easily clone the projects, open them in my window, and be able to work on them. That is the best feature I would recommend.

GitHub has many features, and it can be very good, such as having repositories. Also, some people are using it for the purpose of clearing doubts. There is something called asking doubts with someone else. Common people will be answering, and then I will be able to get badges to showcase on my profile. That is absolutely correct. Even the outcome metrics, such as if someone needs to hire me, they could be able to see my GitHub profile for the committed push and pull methods and all that, so GitHub will showcase my metrics.

Absolutely, it is money saved because instead of buying another cloud platform such as Google Cloud, I can easily maintain a repository and host it. Then it is also fewer employees needed because I do not need a big tech core for managing a database and repositories.

The thing that has frustrated me is sometimes when I push using a Git command, I need to force the push, which is the main thing. The setup is frustrating because GitHub could add a repository with pre-installed packages or something since I need to install packages in VS Code before pushing and maintain it in the codebase. Git packages need to be installed manually, and if that was already in a GitHub repository, that would be much better.

GitHub packages can be installed previously for the project upon the project requirement, and that is the thing I wanted to add here. That would be good.

According to governance and security, I recently heard about some security issues in GitHub. I think that could be centralized and should consider those security issues and clear them. The AI capabilities there include Copilot or something else.

I recently heard about security issues, but I do not know about it clearly. However, if security has been more tightened, it will be better.

I have been using GitHub for the past two to three years.

I have not experienced any downtime or issues. I received news about security issues, but other than that, I did not have any issues with it.

GitHub can handle my projects very well as they grow. I can easily give updates from VS Code and commit messages directly to the GitHub repository by just using Git commands.

I have not contacted customer support because I did not have any issues that required contacting them. I do not think customer support is something I have used, but I think they will be more good, especially when getting new features or offers.

Before using GitHub, I used a Netlify platform for small projects just with a drag and drop option. Later, I learned about GitHub, and then I switched to GitHub for maintaining repositories. Now, GitHub is one of my day-to-day activities.

When I first started GitHub, I thought it was too hard to do, hard to maintain, and the repositories were not being created with a proper method. Then later, I could understand and see many YouTube tutorials to understand GitHub and learn Git commands, which allowed me to easily adapt to GitHub. When I was starting first, I was really frustrated about what this tool was. At first, it was really difficult to understand, but later, after using it for three to five projects, I learned about GitHub. Upon the fifth project, it became very easy for me to maintain a GitHub repository.

I just keep it simple with Git. I have heard about GitLab, but I have not used it. I use GitHub with straight branching strategies, just a straight branch commit.

I have been using GitHub for free, and recently I got a free education offer, such as educational resources. I believe it is GitHub Pro or something similar. I have been using the educational offer, which gave me many resources for free, and I have used GitHub Copilot Pro for free as well. I have not encountered any initial setup cost for that.

I did not evaluate any other options. I just used a manual method in GitHub.

I use a private cloud here and also a public cloud; I use both private and public.

GitHub has many features, and it can be very good, such as having repositories. Also, some people are using it for the purpose of clearing doubts. There is something called asking doubts with someone else. Common people will be answering, and then I will be able to get badges to showcase on my profile. That is absolutely correct. Even the outcome metrics, such as if someone needs to hire me, they could be able to see my GitHub profile for the committed push and pull methods and all that, so GitHub will showcase my metrics.

If a new user is using GitHub, they should first learn about Git commands and directly push the repository, avoiding the drag and drop method. They should understand Git commands and from VS Code or their preferred IDE, they can push and maintain a repository. After pushing to the repository, they should be aware of the use cases of a repository. It is not just to maintain as a cloud; they can use it for hosting and other database connections.

Additional thoughts about GitHub include the potential to provide more resources for GitHub Enterprise. I have not used it, but I believe GitHub Enterprise should be beginner-friendly. My overall rating for this product is 9.5 out of 10.

When discussing my use case, I don't know which vendors we are working with in that area, as it's not my area of responsibility right now. About six months ago, I was promoted to Software Development Manager, and things could be different than they were before. I can give you another phone number at my company for the cybersecurity manager if needed.

I'm working with software development. We have a CI/CD process, and our repository is on GitHub with secure coding checks. We are using most of the DevOps processes in our company.

We can discuss GitHub further. I have been working with GitHub for about five years.

We are using GitHub because it is open-source software, which is the most valuable solution for us. The open source and community support are very good. We are always up-to-date with the community, and integration difficulty is very low. If you integrate any CI/CD solutions on GitHub, it's very easy.

We started using GitHub about three months ago with AI integration. For our deployments, some developers can be very shy about asking for descriptions on their commits. We are using AI support for comments and deployment management, which is beautiful.

We are not using the GitHub API for automating workflows in our projects.

I give GitHub a five-star rating for the review capabilities.

I also give GitHub five stars for integration with third-party applications. There is a lot of integration available on GitHub. If you want to integrate something, even if it could be integrated before GitHub, you can make your code and integrate your own in-house applications. It's a very easy and powerful aspect of GitHub.

Security could make GitHub better. OWASP Top Ten security advisors could be integrated on GitHub, and it could provide checks and advice. That would be much better. Additionally, LLM integration on GitHub could be a very impressive addition and is important.

We are using security alerts on the IDE. We are also a customer of JetBrains, and GitHub is good, but I think it needs a little development for the enterprise level.

I have been working with GitHub for about five years.

I give GitHub a four-star rating for stability because it's an open-source solution. There are some difficult aspects regarding deployment and high availability matters, but we can handle them.

I would rate the scalability of GitHub an eight.

GitHub's most competitive alternative is GitLab. I don't have any experience with other solutions, so I can't make strong statements about them.

The setup process for GitHub is very simple.

We are not using Citrix Endpoint Management. We have a different solution for endpoint management instead of Citrix.

We are not using Secure Private Access or the Citrix Cloud Platform.

GitHub Actions do not increase deployment time. It's actually a very powerful tool for deployments and was our first choice when deciding on GitHub. We have very easy deployments, and we have about two different development teams. Some of them are using Java, and some of them are using .NET. Both disciplines are very stable and have perfect deployment time on GitHub.

We are using forum support for GitHub, and we have a lot of friends on forums. Forums are very important to me. They were the first support on the internet, and I still love the forums.

I can recommend GitHub to other users. I give this review an overall rating of nine.

GitHub serves as our primary platform for source code management, version control, team collaboration, code reviews, CI/CD automation, and issue tracking in software development. We store and manage source code in centralized repositories, hosting web application code in private repositories. We track code changes and maintain history using Git, with the ability to revert to a previous code version if an issue occurs. Code review is crucial to our process, as senior developers review and approve code before merging it into the main branch and running automatic tests after every code commit.

Our team collaborates on GitHub by using it for version control, CI/CD workflows, and collaboration. Developers collaborate on code changes through branches and pull requests. For issue tracking, we track bugs, enhancements, and development tasks by logging bug issues and assigning them to developers.

GitHub is deployed in our organization primarily to store application code, manage branches, review pull requests, and automate deployments. It supports code management, version control, collaboration, and DevOps automation across our software development team.

The best features GitHub offers include version control, repositories, pull requests, code reviews, issue tracking, and automation workflows. These features significantly improve collaboration, code quality, and development efficiency. Our development team uses pull requests and code reviews to validate and merge code changes before production deployment.

Automation workflows in GitHub help my team by providing capabilities through GitHub Actions, which automate software development workflows directly within repositories. Automation features such as CI/CD pipelines, automated build, test, and deployment processes run tests automatically after code commits or pull requests. Regarding deployment automation, we deploy applications automatically to environments, run recurring workflows on schedules, and automate alerts and approval steps. Whenever a developer pushes code, GitHub Actions automatically run unit tests and deploy the application after successful validation.

GitHub has positively impacted my organization by improving collaboration, code quality, version tracking, and development efficiency. It has helped multiple developers work on the same project without overriding code. The specific outcomes since using GitHub include faster code deployment cycles, improved code quality through reviews, better version control and change tracking, reduced code conflicts among developers, automatic testing and deployment workflows, and increased team collaboration and visibility. We see improvements in pull request merge time, deployment frequency, build success rate, issue resolution time, and code review completion time.

GitHub could be improved in several ways. Permission management and access control can become complex in large organizations, and advanced reporting with more built-in analytics and reporting for repositories and team productivity would be beneficial. The cost of enterprise features along with advanced security and enterprise functions can be expensive. Managing repository permissions across multiple teams and projects requires additional governance.

Common challenges I face include repository management, access control, and workflow handling. A pull request may fail to merge because another developer changed the same code section, causing merge conflicts. Common challenges in GitHub include merge conflicts, branch management complexity, permission governance, and troubleshooting automation workflows.

Other improvements needed for GitHub include better reporting, workflow debugging, repository governance, search efficiency, and notification management, such as better filtering of pull requests, issues, and workflow alerts. Easier policy enforcement across multiple repositories is also essential.

I have been working in my current field for five years.

GitHub is generally very stable and reliable, making it more scalable for larger projects. Our team uses it daily for source control and CI/CD pipelines, which indicates that GitHub can support day-to-day development activities with consistent performance and availability.

My experience with customer support is good. Our development team can raise support tickets for repository access issues, billing concerns, and CI/CD workflow problems. Customer support provides proper documentation and knowledge regarding the problems we face, along with good response times.

GitHub delivers a strong ROI by improving developer productivity, accelerating software delivery, and reducing manual effort. It saves money and time while also reducing the number of employees needed due to faster development and better code quality through reviews and lower operational overhead from tool consolidation.

Before choosing GitHub, we evaluated other options such as Azure DevOps and AWS CodeCommit, but we found that GitHub is the best solution for our organization.

Some common challenges I face include repository management, access control, and workflow handling. A pull request may fail to merge because another developer changed the same code section, causing merge conflicts. Common challenges in GitHub include merge conflicts, branch management complexity, permission governance, and troubleshooting automation workflows.

My advice for others looking into using GitHub is that I would recommend it to organizations seeking source code management, team collaboration, and DevOps automation. Development teams can utilize GitHub to manage repositories, perform code reviews, track issues, and automate CI/CD workflows with GitHub Actions, making it a strong choice for organizations that want efficient software development workflows.

GitHub is a strong choice for every organization and is a very good platform for any coder or software developer. It is a fantastic platform for organizations from my perspective. I would rate this product a 9 out of 10.

We built an application for a vendor onboarding platform as a freelance project where the client needed a solution to onboard vendors. We used GitHub for code hosting and deployment. The use case involved onboarding vendors, handling and saving all their data, and pushing it to Kafka so that consumers on the team could use that data.

GitHub helps us to work with the team, manage our code, versioning, and assists us in building. Teamwork and code management are what I used the most.

GitHub has positively impacted my work by helping us to work in parallel on features and ship and deploy them. The impact includes faster collaboration, fewer merge issues, and easy deployment.

GitHub should provide an AI that helps us to put the merge using cherry-picking. Many times we have to do some cherry-pick changes manually, which is not ideal. If there is an AI or agent that can assist us with that, it would be much more helpful.

I think it is still a complex thing. We get options, and there is no centralized UI for GitHub. It varies based on the editor. Every editor has its own separate kind of UI for GitHub, so there is no centric UI or centric plugin that will give all the similar options in all kinds of IDEs.

I have been using GitHub for four to five years in my work. I have used Bitbucket in the sense that we use it in enterprise, which internally is Git only. I have used GitHub for my personal projects, but the majority of the time I have spent on Bitbucket. Whatever the requirement that you are having, based on that you can pivot or you can stay.

GitHub reduces merge issues significantly. Earlier we used to use SVN, specifically TortoiseSVN. From that, we got a 60% reduction in merge issues and merging time, cherry-picking time.

I would rate GitHub overall an eight to nine. My advice to someone considering using GitHub is to go for it. There is no other option better than this currently. I give GitHub an overall rating of 8.

I use GitHub for its repository, and I have also used it for GitHub CI/CD pipeline or GitHub Actions.

I have integrated GitHub with AWS Elastic Beanstalk service for code purposes and also in Azure App Service. After implementation, it is very easy to get code, and we do not need to use any cloud-related repository tools for code storage. So it is very easy.

I only used GitHub enterprise; otherwise, I mostly use the open-source version.

The best feature of GitHub is its branch techniques, and it is very useful for how the branches are managed. This is the best feature I prefer.

Applying GitHub Actions saves so much time for the team because it automates the developer's work to the server.

When working with the CI/CD pipeline and somebody is writing the workflow file, it would be best to include the AI feature so if they write incorrect code, it will notify me about it in the same dashboard, eliminating the need to use third-party tools to review the file.

I use GitHub as it is easy to get code, and we do not need any cloud-related repository tools for code storage.

When working with the CI/CD pipeline and somebody is writing the workflow file, it would be best to include the AI feature so if they write incorrect code, it will notify me about it in the same dashboard, eliminating the need to use third-party tools to review the file. I would like to implement the AI feature, especially in the workflow file.

I have extensively been working on GitHub for the past two years, and my total experience is about five years.

The initial setup of GitHub is very easy and not complicated at all. Especially when we apply it to the CI/CD pipeline as an open-source solution, it is very easy to implement.

GitHub is very stable for me with no performance issues.

GitHub is very scalable.

I have not used customer support for GitHub.

Positive

I was first introduced to GitHub, so I did not use any other solutions for coding purposes because GitHub was my first encounter.

The initial setup of GitHub is very easy and not complicated at all. Especially when we apply it to the CI/CD pipeline as an open-source solution, it is very easy to implement.

If you are new, especially for developers, it is very easy for the first implementation and pushing the code.

I would rate GitHub nine out of ten because if we have complex branch strategies, it becomes very complicated to manage all those branches.

GitHub is very stable for me with no performance issues.

I have not used customer support for GitHub.

I only use GitHub; I have not worked with any other version control systems or products of the same kind.

I have not used GitHub security alerts.

I also have not used GitHub API for automating workflows in my projects.

I am not utilizing code review capabilities in GitHub.

I rate GitHub 9 out of 10.

In my college, I work with three to four students on the same project using GitHub. We create one GitHub repo and push every project into that same repo so all of us can use it without needing to download it locally. When we push into GitHub, we can have eight to ten members or even more working easily. GitHub supports collaboration, whether in a small group or larger, making it easier to share code and organize everything in one place. All I need to do is push from my computer, and they just need to pull into theirs. Initially, I had difficulty understanding at the beginner level, but now I know how to commit, how to push, how to pull, how to sync, and the different functionalities available.

Tracking changes allows me to note when I perform specific changes. When we commit the code, we can add comments regarding the changes, such as what functionality we added or what bugs were solved. This feature helps us track the code at the end of the day, showing what we have accomplished and what still needs to be added, providing effective tracking of changes.

GitHub has made collaboration easier for my team. I have not faced any challenges because we find it easy to use. I only need to handle the database side, so I only need to pull and push within the built-in repo on GitHub.

GitHub always saves time and saves me a lot of time and energy.

If you are a developer who wants to store your code and needs to manage versioning, you can use GitHub for daily ease and to simplify your workflow. I would rate my overall experience with GitHub an 8 out of 10.

I have a developer account on GitHub, my personal account on GitHub. I use GitHub in general for both personal and professional use. I use GitHub, not Copilot specifically for this purpose. It's different across Zühlke Engineering.

I actually appreciate that I can create a developer profile that is outside of work, and that is also technical, not necessarily related to LinkedIn. It shows a more technical profile rather than what I would post on LinkedIn. I have them linked together. I would like to see GitHub expand Copilot to make it more capable of grabbing context by prompt, rather than having to open tabs. If they can enhance it to bring it up to par with Amp, that would be useful.

I would like to see GitHub expand Copilot to make it more capable of grabbing context by prompt, rather than having to open tabs. If they can enhance it to bring it up to par with Amp, that would be useful. I am not so tied to Copilot, as I have been using Amp more in recent months. However, I am providing this feedback for Copilot because it seems more widespread and more companies allow it rather than Amp, and it would be beneficial if they catch up with Amp on this capability.

Regarding my developer profile, I would update it when I have time between projects. I would estimate at least five years of usage, though it may be longer than my time with my current company, which is six and a half years.

I have more than three years of experience, approximately six plus years of experience in my current company. I have been using GitHub for at least five years. I likely used it before joining my current job, but I was not using it that much then. I cannot say I am a heavy user.

I cannot provide an opinion on stability issues. I have not reached out to GitHub support, primarily because I am an infrequent user of GitHub for personal use, and I only use Copilot in projects.

There are projects I was recently involved with that use GitLab, which is a different provider for storing code and deployments. Currently, I am not using GitHub in projects. I have a personal GitHub profile which I keep updated for personal purposes. I use Copilot in projects from GitHub. I do not use GitHub Actions; only Copilot is used in projects. My particular feedback is focused on Copilot as it relates to projects.

I was paying approximately one hundred dollars annually about a year ago. I am uncertain of the current cost, but GitHub without Copilot is free as far as I know. I am not paying anything for my GitHub account.

I am using both Copilot and Amp from Sourcegraph. I am not using the Enterprise version; I am using the professional developer version. It is professional but not the Enterprise version for teams; it is for individual professional developers. I am using Amp Pro, not Amp Enterprise. I have used both the professional licenses for GitHub Copilot and for Amp, not Enterprise licenses.

I believe the integration with the models is seamless. That is a totally different issue than the context-grabbing issue I mentioned earlier, because grabbing context is not related to model processing.

Regarding GitHub security alerts and GitHub Actions, we are not using these features for deployments.

My overall review rating for this product is eight.

My primary use case involves working with GitHub for code management. I have extensive experience using it for various tasks, such as creating repositories, managing pull requests, and utilizing GitHub Actions for automating workflows.

GitHub contributes to efficient project management by providing tools like branch protection features which help in managing multiple environments securely and ensuring quality control before deploying code to production.

I find GitHub's pull request strategies and GitHub Actions to be very valuable. GitHub Actions allow for creating multiple jobs that run in different stages such as build, test, and deploy, which enable better visibility and control over the deployment pipeline.

I would like to see some AI functionality included in GitHub, similar to the features seen in GitLab, to enhance productivity. 

Additionally, offering limited free access to features like Copilot could help newcomers explore and learn the platform more effectively.

I have been using GitHub for approximately six years since the start of my career. It has been an integral part of my professional experience.

GitHub is stable, and I have not encountered any major issues apart from losing access due to the authentication problem. It provides a reliable environment for code management.

GitHub scales well with both public URLs and private server setups, and I have not faced any issues with its scalability.

The technical support from GitHub is generally good, and they communicate effectively. However, they could not assist in recovering access to my account without the multi-factor authentication key, which was unfortunate.

Positive

I have used Bitbucket and GitLab besides GitHub. Each tool has its unique features, but I find GitHub to be exceptional in its offerings.

The initial setup of GitHub, particularly when integrating with AWS services, requires the creation of infrastructure using Terraform, such as VPCs and load balancers. This process can take between one week to a month depending on the project's complexity.

I'm not aware of the costs associated with GitHub. I simply appreciate its efficiency in managing code and collaborating with team members.

I recommend GitHub to those starting in the software development field. It is essential to explore its features, such as repository creation, pull requests, and code management tasks. GitHub is a fundamental tool in the software industry.

I'd rate the solution eight out of ten.

We are using products that are already established, as we are a consultant company that is working extensively on Microsoft technologies. For the queuing products, we are using Service Bus, Event Hub, and Event Grid, the tools in Azure.

At Advania Sweden where I work now, we are working only with Microsoft. In my previous employment at ITAB, we had some resources in Microsoft's Azure, but for the integration work, we were using MuleSoft. In that case, we had some queuing products used in AWS.

Currently, where I work right now, we are only working with Microsoft tools.

For the queuing parts in Azure, we are using GitHub and Service Bus.

We are using Service Bus.

The team is working with Service Bus and I am involved in it. Sometimes I look into the DLQ messages and see what goes wrong and explore how we can do it better.

I am not deeply involved in GitHub security alerts. I work more as a technical lead and solution architect, so the developers are more involved in the GitHub aspects than I am.

The same applies to Azure Service Bus.

I have not heard anything else negative, and they are satisfied with GitHub. GitHub's integrations with third-party applications are quite good for the needs that we have today. We have implemented some features here. When I am ready with some tasks as a developer and I do a pull request, we automatically send that to Slack, to a Slack channel so the other developers see that I am ready with a pull request and can review it.

We have been working on artificial intelligence improvements as well, and improvement of that, so the development and delivery to different kinds of environments will be faster. I think that a slight improvement in that case would be beneficial. I think it is quite good now, but a little bit of improvement would be even better.

I am talking about their artificial intelligence capabilities.

I am not thinking about some specific aspects right now. GitHub works for us.

For the queuing parts in Azure, we are using GitHub and Service Bus.

I rate GitHub as an eight out of ten.

GitHub's pricing is quite reasonable.

The use of GitHub's API for automating workflows is done through automation workflows.

I would rate this review as an eight.

Neutral