On my quasi-blog: "Git without a forge"
https://www.chiark.greenend.org.uk/~sgtatham/quasiblog/git-no-forge/
Most of my projects are hosted in bare git repositories on the web, and not on a forge site. I talk a bit about this: ways to send patches to a project like that (and which I personally prefer), and reasons why I haven't (yet?) changed my arrangements.
@simontatham While I'm not at all trying to persuade you to use GitLab, I thought it might be worth mentioning that everything in the "You get a workflow imposed on you" section is mistaken, at least for GitLab. You can turn most features on and off, including whether issues or merge requests are enabled for a given repository. For example, repositories on Debian's GitLab instance frequently have issues disabled to avoid duplicating the Debian bug tracking system.
@cjwatson thank you, I had indeed not known that! I've added a note to that section.