The community submitted 658 reviews to tell
us what they like about GitHub, what GitHub can do better, and
more.
5.0
Based on 658 reviews
Review GitHub?
Reviewers describe GitHub as the default home for code: a reliable place for version control, pull requests, issues, reviews, releases, and CI/CD that keeps teams aligned and helps solo developers ship faster. Users repeatedly praise its deep integrations, open-source community, and tools like Actions and Pages. Makers of Warp and TestMu AI echo that, highlighting public repos, PRs, issues, and built-in CI in one place. Main complaints are complexity for beginners, confusing advanced settings, weak mobile and search, occasional slowness, and pricing friction.
+663
Summarized with AI
Pros
Cons
Tines The single, secure environment for agents, apps, and automations.
Distribution, the site and CI ended up being the same place, which I didn't
expect. The plugin marketplace is a repo — people install claudemon by typing
`/plugin marketplace add zamarrowski/claudemon`, so there's no registry, no
publish step and no account for anyone. Pages serves the landing straight out
of `docs/` with no build. Actions runs the tests.
We chose GitHub primarily because of its ecosystem, developer adoption, and integration advantages.
For a developer infrastructure product like EasyBilling, being close to where developers already collaborate matters a lot. GitHub has become the default platform for open-source communities, AI tooling, API products, and developer ecosystems, which makes it easier for us to:
• collaborate with external contributors
• share SDKs and documentation
• integrate with developer workflows
• build visibility within the AI developer community
We also found GitHub’s integrations, Actions ecosystem, and overall developer experience particularly strong for fast-moving startup teams.
GitLab is a very capable platform as well, especially for enterprises that want a more integrated DevOps stack or self-hosted workflows. But for our current stage, speed, ecosystem reach, and developer familiarity were more important priorities.
As an AI infrastructure startup, we optimize heavily for developer adoption and iteration speed, and GitHub aligned better with those goals.
The entire release path is Actions: lint, typecheck, build, validate the MV3 manifest, then emit a Web Store-ready zip. Changesets and Dependabot plug straight in — no separate CI to babysit.
GitHub was the natural choice because it is almost indispensable for file management, folder structure, version control, and developer workflows.
I used GitHub because it made the project easier to organize and manage. Keeping the codebase, folders, branches, updates, and collaboration flow in one place helped me work in a much more controlled and professional way.
For a project with many files, agents, features, and platform-specific parts, GitHub became the safest way to track everything. It helped me avoid confusion, manage changes clearly, and keep the development process clean.
Overall, I chose GitHub because it is an industry-standard tool for code storage, file management, version control, and structured development. For this kind of project, it felt like the most reliable and necessary option.
GitHub is how Troopr knows what actually shipped versus what was said. It reads PRs, commits, and the diffs behind them, so a vague commit message can't hide real work. It's the signal that grounds every standup against reality.
Huge shoutout to GitHub for their amazing Gist service! Yist wouldn't exist without it. Their robust API and reliable platform have been the backbone of our app, allowing us to bring the power of Gists to your desktop. Thanks GitHub for fostering code sharing and collaboration!