"SSH / GPG Keys" settings point to GitHub docs instead of Codeberg#940

Open
opened 2023-02-15 02:43:16 +01:00 by NeatNit · 0 comments

Repeating what I mentioned on Mastodon, since I searched for older issues and found none.

Go to SSH / GPG Keys: https://codeberg.org/user/settings/keys and you'll see links to GitHub doc pages:

Need help? Have a look at GitHub's guide!

Codeberg has its own docs for these topics:

https://docs.codeberg.org/security/ssh-key/ Adding an SSH key to your account

https://docs.codeberg.org/security/gpg-key/ Adding a GPG key to your account

(There is no equivalent of GitHub's troubleshooting page, though, from what I can tell)

It would be nice if Forgejo pointed to these instead of GitHub. I looked a little deeper, and I believe the source of this text is:

https://codeberg.org/Codeberg/forgejo/src/branch/codeberg-1.18/templates/user/settings/keys.tmpl the template for the entire Keys page

https://codeberg.org/Codeberg/forgejo/src/branch/codeberg-1.18/templates/user/settings/keys_ssh.tmpl#L100 (permalink) the template for the SSH section, inserting the linked URLs

https://codeberg.org/Codeberg/forgejo/src/branch/codeberg-1.18/templates/user/settings/keys_gpg.tmpl#L112 (permalink) the same for the GPG section

https://codeberg.org/Codeberg/forgejo/src/branch/codeberg-1.18/options/locales/gitea_en-US.ini#L662-L663 (permalink) the localization strings, for en-US

Note, of course, that all 30 localizations would need to be updated if the links are changed.

Repeating what I mentioned [on Mastodon](https://fosstodon.org/@neatnit/109865943396657326), since I searched for older issues and found none. Go to SSH / GPG Keys: https://codeberg.org/user/settings/keys and you'll see links to GitHub doc pages: ![Need help? Have a look at GitHub's guide!](/attachments/b8bd2a25-d490-4c19-9a97-a50bf2e96064) Codeberg has its own docs for these topics: https://docs.codeberg.org/security/ssh-key/ Adding an SSH key to your account https://docs.codeberg.org/security/gpg-key/ Adding a GPG key to your account (There is no equivalent of GitHub's [troubleshooting page](https://docs.github.com/en/authentication/troubleshooting-ssh), though, from what I can tell) It would be nice if Forgejo pointed to these instead of GitHub. I looked a little deeper, and I believe the source of this text is: https://codeberg.org/Codeberg/forgejo/src/branch/codeberg-1.18/templates/user/settings/keys.tmpl the template for the entire Keys page https://codeberg.org/Codeberg/forgejo/src/branch/codeberg-1.18/templates/user/settings/keys_ssh.tmpl#L100 ([permalink](https://codeberg.org/Codeberg/forgejo/src/commit/1f31b235b813e58939a0b4565ab173e1f34180be/templates/user/settings/keys_ssh.tmpl#L100)) the template for the SSH section, inserting the linked URLs https://codeberg.org/Codeberg/forgejo/src/branch/codeberg-1.18/templates/user/settings/keys_gpg.tmpl#L112 ([permalink](https://codeberg.org/Codeberg/forgejo/src/branch/codeberg-1.18/templates/user/settings/keys_gpg.tmpl#L112)) the same for the GPG section https://codeberg.org/Codeberg/forgejo/src/branch/codeberg-1.18/options/locales/gitea_en-US.ini#L662-L663 ([permalink](https://codeberg.org/Codeberg/forgejo/src/commit/1f31b235b813e58939a0b4565ab173e1f34180be/options/locales/gitea_en-US.ini#L662-L663)) the localization strings, for en-US Note, of course, that all 30 localizations would need to be updated if the links are changed.
NeatNit changed title from user/settings/keys points to GitHub docs instead of Codeberg for SSH, GPG to "SSH / GPG Keys" settings point to GitHub docs instead of Codeberg for SSH, GPG 2023-02-15 03:01:56 +01:00
NeatNit changed title from "SSH / GPG Keys" settings point to GitHub docs instead of Codeberg for SSH, GPG to "SSH / GPG Keys" settings point to GitHub docs instead of Codeberg 2023-02-15 03:02:28 +01:00
Gusted added the
enhancement
Codeberg
labels 2023-02-17 20:13:45 +01:00
n0toose added the
s/Forgejo
contributions welcome
labels 2023-04-09 19:39:30 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Codeberg/Community#940
No description provided.