Thanks, but I do not intend to merge this.

You could maintain this in a separate repository and take full responsibility for it, while we wait for me to implement support in forge directly.

Forge has a lot of technical depth. For months now I have been working on slowly paying it off. Next month I plan to turn my focus on paying of the technical depth related to supporting another forge in addition to github (i.e., gitlab). Once that is payed off it will be possible to add support for additional forge, without going deeper into depth.

This pr is based on someone else's pr, #610, which wanted to add gitea support. The reasons I gave there for not merging that, also apply here. By the ways, after #610 I actually did work on gitea support myself a bit (because of the reason mentioned at magit/ghub#171 (comment)), but it quickly became clear that indeed it would be better to first improve forge-gitlab.el, before copying that to forge-gitea.el and adjusting to actually support gitea.

That being said, if you actually do end up maintaining a forge-forgejo.el, I think you would be better of basing that off a contemporary forge-gitlab.el instead of the old forge-gitea.el you picked.

As mentioned at magit/ghub#170 (comment), I do actually plan to add support for Forgejo, but this is still a few months off. It most likely will happen this year though.