#145 (comment) explains you can manually configure GCM to authenticate to a Gitea instance by OAuth. Better would be to automatically recognise Gitea instances by WWW-Authenticate header (populated by Gitea 1.21 and later):
Www-Authenticate: Basic realm="Gitea"
The OAuth configuration is universal across instances: client id e90ee53c-94e2-48ac-9358-a874fb9e0662 , and endpoints /login/oauth/authorize and /login/oauth/access_token.
Gitea v1.21 instances to test against: https://try.gitea.io/ and https://next.forgejo.org/
#145 (comment) explains you can manually configure GCM to authenticate to a Gitea instance by OAuth. Better would be to automatically recognise Gitea instances by WWW-Authenticate header (populated by Gitea 1.21 and later):
The OAuth configuration is universal across instances: client id e90ee53c-94e2-48ac-9358-a874fb9e0662 , and endpoints
/login/oauth/authorizeand/login/oauth/access_token.Gitea v1.21 instances to test against: https://try.gitea.io/ and https://next.forgejo.org/