GitLab is quite good, the organizational features and CI is also mostly on par with GitHub. You can use gitlab.com, SaaS or self-host.

Self-hosting. If you really need to push remotely, push to bare repo on your own cloud vm or setup gogs or forgejo.

I now start with local repos first and whatever I deem OSS-useful, I mirror-push from local to Github or anywhere else with forgejo.

Github was never really needed to use git for private projects.

Forgejo is super easy to set up on a 1-2 core vm. Make a compose file and put caddy in front for tls. the whole thing is less than 50 lines and costs about $10-$15 a month.

Sourcehut.

Uses the same email-based patch workflow as Linux. Takes an hour to learn, and they have helpful guides: https://git-send-email.io/. No JavaScript.

Azure DevOps <shudder/>

GitLab. We self-host ours and it's rock solid.

self hosted Gitea is my recommendation. has everything one needs and is super lean and resource saving. you can run it easily on a 1GB VPS - I even ran it for a while on 512MB.

If it's for work, why do you need GitHub at all?

To me, GitHub only makes sense as a social media site for code. If you are publishing to GitHub with no intent to be open in your code, development process, and contributor roster, then I don't see the point of being on GitHub at all.

Because it's not like their issue tracker is particularly good. It's not like their documentation support is particularly good. It's not like their search is particularly good. It's CI/CD system is bonkers. There are so many problems with using GitHub for its own sake that the only reason I can see to be there is for the network effects.

So, with that in mind, why not just setup a cheap VPS somewhere with a bare git repo? It'll be cheaper than GitHub and you don't have to worry about the LLM mind virus taking over management of your VPS and injecting this kind of junk on you.

Codeberg seems to have legs. License is different, best read it.

Gitlab.