I use GitHub regularly for freelance web development projects, MCA academic work, and collaborative coding tasks. It helps me manage repositories, track code changes, maintain backups, and organize project versions efficiently. I mainly use GitHub with VS Code while working on frontend and backend development projects.

The branching and commit history features are especially useful when testing new updates or fixing bugs without affecting the main project. I also use GitHub to store project documentation, collaborate on shared code, and manage deployment-related workflows. The platform feels reliable for both personal and professional development work. Review collected by and hosted on G2.com.

For new users, some advanced Git workflows like rebasing, resolving merge conflicts, and managing multiple branches can feel confusing at first. Large repositories can also become difficult to navigate if projects are not organized properly. However, after regular use, the workflow becomes much easier to understand. Review collected by and hosted on G2.com.

What I like best about GitHub is the way it combines version control, collaboration, and project organization in one place. It makes it easy to track changes, review code through pull requests, and work with others on the same project without losing the history of what happened. Review collected by and hosted on G2.com.

What I dislike most about GitHub is that it can feel cluttered and overwhelming, especially when you’re juggling issues, pull requests, notifications, and project boards at the same time. Review collected by and hosted on G2.com.

I appreciate GitHub for its robust code management across environments and its seamless pull request workflow. The platform offers near real-time updates when code is reviewed, approved, and merged, which improves collaboration efficiency. Additionally, its strong integrations with tools like Databricks, GitHub Copilot, PyCharm, and VS Code enhance overall developer productivity. Review collected by and hosted on G2.com.

There is very little I dislike about GitHub overall; however, the repeated need to configure or refresh authentication tokens can occasionally be inconvenient and disruptive. Review collected by and hosted on G2.com.

Using GitHub for storage was simple to use and up all the time. It was easy to set up and get started with commits of new APIs version while keeping it easy to update new version over time. Review collected by and hosted on G2.com.

Not much to dislike as the system was performing as expected. Maybe we could get a security related error code instead of 404 when the URI is defined, but you do not have access, like with https://github.com/apiaryio/documentation-service. Review collected by and hosted on G2.com.

Github is one of the most used devtool for developers. it basically keeps track of historical changes to your code and provides tools to allow multiple people to make changes to the code without stepping on each others toes. If you and another developer both have copies of a git repository and you both make changes to your copies, git will let you merge them in a sensible way without anyone's changes being overwritten.

Github itself is the most popular public host for Git. It allows us to use all the features of Git, along with a useful UI and a social aspect. It's value is that it is a service for hosting git repositories where multiple people can access them, with some nice additional features built on top. It also helps during experimentation to be able to make alternate versions of your code (branches), that you can swap back and forth between. Review collected by and hosted on G2.com.

errors and messages are not self-explanatory and requires the user to take time out and spend it learning. If this was meant for non-coders then this would be marked as bad UX. But coders are too harsh on each other and expect other coders to run through UX simply because they are coders and are supposed to just deal with that. the workflow is efficient but it has been evolved and expanded so much from years that makes it a bit complicated too. i have seen many users facing shadow bans for literary no reasons. recently GitHub has faces many downtime and performance issues too due to high traffic and increasing usage of the platform due to AI coding. GitHub has been a chokepoint for coding workflows, if its down many things can go wrong which makes the uptime and availability of GitHub essential. Review collected by and hosted on G2.com.

Out of the many things I like, the GitHub Issues connectivity with the Change Request stands out. I also appreciate how easy it is to implement GitHub Actions, along with the wide variety of deployments that can be performed through GitHub Actions.

Another great feature is GitHub Copilot. It helps me tackle many complex tasks, and I like that it can make modifications and raise a change request directly through Copilot itself, without needing as much manual intervention.

I use this very frequently with all of my projects and have a very smooth experience.

I initially used some other tool, but then migrated to Github and the integration and onboarding was very easy and smooth. Review collected by and hosted on G2.com.

I wouldn’t describe this as something I dislike, but it can be challenging to learn as a new beginner. For example, when a project has multiple microservices in a single Git repo, setting up GitHub worktrees can become tricky. This is especially true when there are microservice-level configuration files that may differ depending on the branch you’re working on. There may be a solution for this, but I’ve found it a bit difficult to work with so far. Review collected by and hosted on G2.com.

What I like best about GitHub is that it makes it easy to manage code changes and collaborate with others without things getting messy. Pull requests, commits, and issues help keep track of work properly, especially when working on projects with multiple people. I also use it a lot to explore open source projects and learn from real codebases. Review collected by and hosted on G2.com.

What I dislike is that GitHub can sometimes feel confusing when dealing with merge conflicts, permissions, or large repositories. Review collected by and hosted on G2.com.

Ease of code maintenance, standard procedures, everything at one place, enough options to do what I need.

What I like best about GitHub is how it combines version control, collaboration, and CI/CD into one seamless platform. The pull request workflow, issue tracking, and integrations make teamwork and code reviews efficient. It’s become the central hub for managing projects from idea to deployment. Review collected by and hosted on G2.com.

Setup on.local, issues are not categorised in the best way, vauge filters are used, tough to find the issue I'm searching for, e.g..The UI can feel cluttered and some advanced features are hidden behind multiple menus, which slows down navigation. Pricing for private repos and advanced CI/CD minutes can also become expensive for teams. Occasionally, large repos or Actions pipelines feel slower than expected. Review collected by and hosted on G2.com.

What I like most about GitHub is that it centralizes the entire development cycle in one place. It's not just a Git repository: it also functions as a collaboration and automation platform. Pull Requests, with a structured code review, elevate code quality and require you to justify technical decisions before integrating changes. GitHub Actions allows you to incorporate CI/CD directly into the repository, which simplifies automated testing, builds, and deployments without relying on external tools. I also value the clear management of branches, branch protection, and permission control, because they help maintain standards when working with large teams. In both personal and professional projects, GitHub reduces operational friction and improves code traceability. Review collected by and hosted on G2.com.

GitHub can become complex when working with large teams if workflows are not clearly defined. Setting permissions, protected branches, and Actions is not always intuitive, and sometimes it's difficult to find the right way to get everything properly adjusted. Additionally, some more advanced features depend on paid plans, which can end up limiting small teams. Review collected by and hosted on G2.com.

GitHub's UI is genuinely clean — navigating across repos, PRs, Actions logs, and security alerts never feels cluttered even on large codebases. The onboarding for new contributors is handled well too; a good README + GitHub Pages setup and people can start contributing without any hand-holding. Integration with the entire toolchain (HuggingFace, PyPI, DockerHub, Slack) is seamless. For projects like PromptWall, I had CI running, a dataset linked, and a release pipeline live within a day of going public. Copilot suggestions inside PRs are actually useful for catching obvious issues during review. Review collected by and hosted on G2.com.

Free tier Actions minutes cap is a real bottleneck once you have multiple active repos. Performance on the web editor lags noticeably on large diffs — anything over 1000 lines becomes painful to review in-browser. Secret scanning false-positives are annoying for security research repos (flags test credentials in CTF writeups). Support response time on billing/account issues is slow; the docs are thorough but finding answers to edge cases takes too long. Review collected by and hosted on G2.com.