Gitea has every feature that Gogs had at the point when they forked it, plus a few that they've ported over.
But there are still features that have been in Gogs for over a year now that Gitea does not have.
One example that burned me earlier this year, Gitea's backup/restore feature is still very underdeveloped. Gogs' backup/restore feature has been capable of backing up and switching databases for over a year, while Gitea still can only backup and restore to a database of the same type (e.g. Postgres to Postgres)
Also, thanks for noting this. I had the mental perception that Gogs had really been fully surpassed by Gitea, and I need to re-evaluate now. Thanks.
Doubtful. IIRC it was somewhat of a hostile & opportunistic fork. The Gogs maintainer went on vacation or something and didn't reply to issues for a couple weeks so someone forked to Gitea and declared themselves the new mainline only for the Gogs maintainer to return and not appreciate the attempted usurpation.
You had that perception for good reason: it had surpassed GoGS. But they're both moderately active projects so it's good to revaluate regularly.
Gitea on the other hand was to be more of a community project with multiple maintainers and ways for active contributors to become one.
Though Gogs has more stars, and currently, I think, more related project/integrations, looking at GH stats, Gitea has more activity, PR's, commits, etc.
That made me choose Gitea over Gogs. Really content with it.. was planning on using Gitlab at first, but it would require AWS instances with double the oomph.
The documentation could be better, agree, but a search in issues or filing a Help wanted issue comes a long way.
Why compare two products by their README and not their website? Heck, why not compare them by using their test instances that are there for you to try.