Why I use it
Its job in the stack
I use GitHub to keep source changes inspectable and connected to issues, pull requests, checks and deployments. A reviewed repository provides a far safer production path than editing a live server by hand.
The platform supports the process, but branch rules, tests, secrets and release ownership determine whether that process is dependable.
Where it earns its place
Work I use it for
- 01Git repositories
- 02Pull requests
- 03Automated checks
- 04Deployment workflows
Limits
What it does not solve
Repository access and automation tokens are consequential credentials. Large binaries and secrets do not belong in ordinary source history.