Github Reviews & Ratings

4.6/5

“Massive Integrations & Ecosystem”

I rely on tools for linting, code formatting, dependency scanning etc. GitHub lets me plug in these tools easily via marketplace or webhooks. That reduces maintaining custom glue scripts.

Pros : Integrates with many tools, CI, GitHub Apps, VS Code, issue trackers, bots, etc. The ecosystem is huge.

Cons : Sometimes third-party integrations break with updates; marketplace discoverability for apps isn’t always perfect.

Switched from : Razorops

Reason to switch : I moved from self-hosting because maintaining integrations and plugins was time-consuming; GitHub handles a lot of that out of the box.

4.6/5

“GitHub Actions Makes CI/CD So Much Easier”

Before, I used separate CI tools and manually integrated with repos. When I moved to GitHub, using Actions means I don't jump between tools; code, builds, tests are closer together. It cuts down setup time.

Pros : Built-in CI/CD, Actions marketplace, automations directly in the same platform as the code.

Cons : Action workflows can get complex; debugging CI failures sometimes takes a lot of trial & error.

Switched from : Jenkins

Reason to switch : I left Jenkins because managing servers was a headache; I switched to GitHub so that CI/CD would be more integrated, zero-maintenance from my side.

4.5/5

“Free Tier Is Very Useful, Premium for Enterprises”

For small projects, hobby projects, open source, GitHub free is more than enough. As teams grow, features like audit logs, SAML SSO, compliance become indispensable, though they cost.

Pros : The free tier for public repos is generous; unlimited collaborators; GitHub Student for students. For teams, paid tiers add advanced features.

Cons : Some advanced security/compliance/team management features are behind higher cost plans; enterprises may need GitHub Enterprise which is expensive.

Switched from : Gitlab

Reason to switch : I moved from a free GitLab self-hosted instance because maintenance costs and backups became burdensome. GitHub’s free/premium model gave me better infrastructure, reliability, and fewer administrative burdens.

4.5/5

“Codespaces & Cloud Dev Are Game-Changers”

Earlier, we onboarding developers often involved local setup challenges. Now, with Codespaces, environments are launched quickly, enabling developers to begin coding immediately & boosting overall productivity.

Pros : Codespaces offers a ready-to-use cloud development environment, making it easy to start coding right away without the hassle of local setup.

Cons : The service can be pricey, and its speed is tied to internet quality. Certain configurations may still take extra time.

Switched from : Vagrant

Reason to switch : I moved from local setup + Vagrant because environment drift was a headache. GitHub Codespaces gave consistency and faster onboarding.

4.5/5

“Great for Teams & Private Repos”

For work projects, I need tight control over code access. GitHub gives me features like branch protections, required reviews, audit logs. That helps in maintaining quality and security.

Pros : Private repositories, team permissions, code review, protected branches—all work well.

Cons : Pricing for private repos in larger teams can get expensive; some enterprise security features require advanced plans.

Switched from : Bitbucket

Reason to switch : I used Bitbucket before; but found GitHub’s review workflows and community support better. Switched so team felt more comfortable using tools many are already familiar with.

4.5/5

“Dependabot and Security Alerts Are Valuable”

I used to manually monitor dependency updates. With GitHub’s built-in tools, many updates come automatically, and security risks are flagged early. This is important for long lived projects.

Pros : GitHub’s automatic dependency scanning, vulnerability alerts, Dependabot PRs help me keep projects secure.

Cons : False positives or outdated advisories sometimes; alerts need tuning to avoid noise.

Switched from : Snyk

Reason to switch : I switched because manually tracking dependency vulnerabilities was error-prone. GitHub’s integrated tools saved time and increased project security.

4.5/5

“Excellent Version History & Offline Work”

Having full history locally lets me experiment without fear. Also when I’m offline, I can still commit and work, only pushing when back online. GitHub (with Git) supports that really well.

Pros : Git’s distributed nature on GitHub lets me commit locally, branch freely, merge confidently. Good history & rollback.

Cons : Merge conflicts can still be painful; large repos can get slow.

Switched from : SVN

Reason to switch : I switched from SVN because I was frustrated that I couldn’t commit when offline and branching was more cumbersome. Git + GitHub gave me freedom and better branching/merging support.

4.3/5

“Excellent for Open-Source Collaboration”

When I started contributing to open-source, GitHub was the natural place. I can see other people’s code, collaborate easily, fork & branch with minimal friction. GitHub’s social and collaborative tools (stars, watchers, issues) help me engage with other devs.

Pros : GitHub gives me the largest community exposure; pull requests, issue tracking, code reviews, wikis & Discussions all in one place.

Cons : Sometimes the UI can feel busy; permissions and billing can get confusing when transferring between personal/org accounts.

Switched from : Gitlab

Reason to switch : I switched from GitLab because GitHub’s community is much larger and more visible, my open-source work got more exposure and contributors when hosted on GitHub.

4.3/5

“Large Community & Network Effect Helps Visibility”

When I host open-source projects on GitHub, I get more external contributions, issues, feedback. That helps improve quality, and also helps me network.

Pros : Public repositories get visibility; code gets forked/contributed to; GitHub rankings, trending repos, stars help showcase work.

Cons : Discoverability sometimes favors very large or popular projects; newer tools/features may be slower to reach smaller users.

Switched from : Gitlab

Reason to switch : I switched because GitLab (while excellent) had less discoverability and external visibility for open-source—GitHub gives more exposure and potential contributors.

4.3/5

“Great for Documentation & Community Support”

When working on side projects, I appreciate that GitHub lets me host documentation, micro-blogs, Gists without needing separate sites. The community helps me discover tooling, fixes, and improvements.

Pros : GitHub Pages, wikis, Discussions, issues, Gists—all integrated. Enough community to find help, code examples, tutorials.

Cons : Managing many issues/discussions across repos can get overwhelming; spam or low quality contributions sometimes happen.

Switched from : Gitlab

Reason to switch : I moved from separate documentation sites + basic code repos to GitHub because having everything under one roof (code + docs + community) cuts down context switching.