
GitHub
How people build software
5.0•669 reviews•11K followers
How people build software
5.0•669 reviews•11K followers

11K followers
11K followers
GitHub is where I manage most of my software projects, especially open-source ones. It brings version control, pull requests, issues, code review, CI/CD, and collaboration together in one place. GitHub Actions is also a big part of my workflow, making it easy to automate testing, builds, releases, and other development tasks.
The open-source community is probably what I value most. It's much more than just a place to host Git repositories.
GitHub can feel overwhelming, especially for newcomers. There are many features, settings, and different workflows to learn, and the interface can sometimes feel more complex than necessary. A more streamlined experience for common development workflows would make it easier to get started. (settings, conflicts, actions, etc..) Also last one month github have some performance issues
I've used and considered alternatives(bitbucket, gitlab(also love it), but GitHub has the strongest combination of developer ecosystem, open-source adoption, integrations, and collaboration features. The fact that so many projects and developers are already there makes it the easiest platform for collaboration.
GitHub is the backbone of almost every serious product workflow I’ve worked on. For me, the value is not just storing code - it is branches, pull requests, code review, issues, Actions, and keeping deployment workflows connected to the actual engineering process.
I’ve used it across full-stack SaaS work, CI/CD pipelines, production deployments, and team collaboration. The PR workflow is especially useful because it creates a clean place to review changes, discuss implementation details, and keep project history understandable. GitHub Actions has also been a big part of my workflow for automated deployments and CI/CD. Once the repository structure and secrets are set up properly, it becomes much easier to ship consistently without turning every deployment into a manual process.
GitHub can still feel heavy when repositories grow and workflows become complex. Actions are powerful, but debugging failed CI/CD runs can take time, especially when the issue is related to environment variables, permissions, or cloud authentication.
I’d like better first-class visibility for deployment pipelines, secrets, and workflow debugging. The product is excellent, but there is still a learning curve when moving from basic repositories to production-grade automation.
I choose GitHub because it has the strongest ecosystem around modern software development: pull requests, Actions, integrations, documentation, issues, security features, and team workflows all in one place.
For startup/product work, the biggest advantage is that almost every tool connects to GitHub first — deployment platforms, analytics workflows, AI coding tools, project management, CI/CD, and open-source references. That makes it easier to keep the engineering workflow simple.
GitHub is the backbone of everything I build. Version control, CI/CD, issue tracking, pull requests, it's all in one place and it just works. The collaborative features (code review, branch protection, Actions) mean I ship faster and catch problems before they hit production. For any developer or team, it's non-negotiable infrastructure.
The pricing jump from free to Team feels steep for small indie teams. Search across repos could be faster and more intuitive. The Projects feature (boards/tables) is getting better but still feels like it's playing catch-up with Linear or Notion. And the mobile app is functional but bare-bones, reviewing PRs on mobile is still painful.
GitLab was the main alternative, solid self-hosted option with built-in CI. Bitbucket too, especially for Jira-heavy teams. But GitHub's ecosystem (community, integrations, Actions marketplace, Copilot) made it the clear winner. Nothing else has the same network effect, if you're open-source, GitHub is where your users already are.
GitHub has become an essential part of modern software development. It provides reliable version control, seamless collaboration through pull requests, issue tracking, and powerful automation with GitHub Actions.
What I appreciate most is its massive developer and open-source community. Whether working on personal projects, client work, or large team collaborations, GitHub makes it easy to manage code, track changes, review contributions, and deploy applications efficiently.
For developers, GitHub is more than a code repository—it's the standard platform for building, sharing, and maintaining software.
The interface can feel complex for beginners, especially around permissions, actions, branches, and repository settings.
GitHub has the best developer ecosystem, strong open-source community, reliable repository hosting, pull request workflow, issue tracking, and GitHub Actions for CI/CD. It is also easier for clients and teams to collaborate because most developers already use it.
GitHub is fantastic because it seamlessly integrates version control, collaboration, and automation into one unified developer platform. It not only makes code sharing effortless but also enables teams to work transparently, efficiently, and at scale. The ecosystem around pull requests, CI/CD, code review, and community contributions elevates the entire development workflow and empowers engineers to build better software together.
We chose GitHub because it provides the most comprehensive and mature ecosystem for modern software development. Its seamless integration of version control, collaboration tools, CI/CD, security features, and open-source communities makes it the most reliable platform for teams of any size. GitHub’s user experience, extensibility, and strong community support allow us to develop, review, and ship software more efficiently than any alternative.
As a solo founder, GitHub is the absolute backbone of my daily development workflow. It is an incredibly powerful platform that acts as my safety net and infrastructure, though it does come with a few structural trade-offs when you are managing everything alone.
When you are the only developer, you are also your own QA and DevOps. GitHub’s robust version control, commit tracking, and branching capabilities allow me to move fast and break things safely. It ensures I have a flawless history of every change and a guaranteed rollback plan if something goes wrong.
The sheer breadth of GitHub's features introduces significant complexity. As a solo founder, my time is severely constrained. Having to spend hours reading documentation to master advanced features, optimize complex GitHub Actions, or untangle Git conflicts is a frustrating hurdle when I just need to be shipping product.
Solid version control and powerful CI/CD. GitHub Actions make automating builds and deployments effortless.
It's so woven into how I work that I forget to appreciate it. Every project I've ever shipped lives here, Pages hosts my landing pages for free, and Actions quietly handles the boring stuff. For a solo builder it's basically free infrastructure.
The mobile app still feels like an afterthought, and search across a big repo can be hit-or-miss. But it's the closest thing I have to a home base.


