You probably don't need GitHub
All too often, I would start a new project on GitHub, only for it to gather dust. It’s one of the reasons I moved my personal projects to SourceHut: I don’t need the social interactions GitHub provides. I still have a couple of larger Rails applications that I host on GitHub, using a separate account.
A minor revelation struck me last night when I was trying to merge another pull request for one of these Rails applications. I probably don’t need to merge this pull request or any other pull request. Since I’m the only one with access to the repository, I can skip creating, monitoring, and merging pull requests and simply use git merge when I am ready to merge the branch into the main Git branch.
Why am I even using issues, projects and milestones in GitHub? Again, it’s just me on the repository, and I don’t need to collaborate in the sense that GitHub allows.
The only reason I am left with using GitHub is that the hosting provider my Rails application runs on uses Git to track changes and automatically deploys them to the server when changes are detected. I have it set up to use GitHub.
Suppose I can handle deploys on another Git service or even from my local laptop. In that case, I can switch away from GitHub for this account.
Still, when it’s just you and the repository, you probably don’t need several of GitHub’s features or even GitHub itself. Just a remote Git repo, and there’s plenty of other options out there.