What to check first
Review the instance and repository role permissions, then test a signed change on a scratch project.
Choose a KeySigner setup
| Setup guide | What it does and what to keep available |
|---|---|
| Test a Forgejo browser sign-in code → | Enroll a fresh code and verify a browser sign-in to the test instance. You need KeySigner on iPhone or Mac with Sign-in codes. Keep available Keep Forgejo’s single-use recovery key where you can reach it outside KeySigner. |
| Replace a Forgejo browser sign-in code → | Check whether a browser stays signed in, then verify the replacement and rejection of the old code. You need KeySigner on iPhone or Mac with Sign-in codes. Keep available Keep independent recovery and the original settings session until the fresh sign-in works. |
What it covers
Access to the release page and verification of the downloadable artifact are separate checks.
Troubleshooting
Does Forgejo still reject your code after replacement?
Check the server address and which entry in KeySigner came from the new QR code. Try a fresh code in a clean session and keep independent recovery available.
Replace Gitea and Forgejo sign-in codes →
Ask the operator of the Forgejo hostname you use to check its maintenance notices and service health. For repositories on Codeberg, use its hosted status report. Check Codeberg status →
Documentation and support
Forgejo documentation
Review instance settings for signed commits
Reset two-factor authentication for a test user