Without explicit configuration, the "wrong" client ID for Codeberg is picked

[manuelprinz]

While contributing documentation to Codeberg on how to use OAuth, we had some confusion about the client ID used by GCO (246ca3e8-e974-430c-b9ec-3d4e2b54ad28), because it works, but no reference to it was found. I only realized late that it seems to be the ID of client registered by @hickford.

Codeberg uses the same client ID as Forgejo (a4792ccc-144e-407e-86c9-5e7d8d9c3269) for GCO. However, it does not seem to be used by default if no configuration is present. (Checked with -verbose on versions 0.17.2 and earlier.) The only way to get that behaviors is to set git config --global credential.https://codeberg.org.oauthClientId a4792ccc-144e-407e-86c9-5e7d8d9c3269.

I think it would be better to use the client provided by Codeberg, not a user-defined one.

P.S.: It is also confusing because both clients have the same name in the application settings, so there is no way to find out which one is which.

[hickford]

I don't think it matters. Both client IDs work. I'm hesistant to change anything that might confuse existing users.

It is also confusing because both clients have the same name in the application settings, so there is no way to find out which one is which

Agreed.