Skip to content

CodeOtter v0.4.0 - Forgejo, Gitea and unified OAuth

Choose a tag to compare

@dharmeshgurnani dharmeshgurnani released this 30 Sep 17:34
· 136 commits to main since this release

CodeOtter now supports GitHub, Forgejo and Gitea in the same installation. Provider connections and sign-in settings are consolidated under one Admin / OAuth sidebar link.

Changes

  • Add Forgejo and Gitea OAuth sign-in with PKCE. Sign-in provider and repository access are independent.
  • Review private repositories, load root guidelines (including fork heads), inspect linked issues and commit history, re-review new commits, update PR comments and post inline suggestions on both self-hosted providers.
  • Keep credentials, repository settings, reviews and organization scopes separate across providers, including identically named repositories.
  • Consolidate server URLs, access tokens, connection tests and OAuth credentials under Admin / OAuth. Old provider settings links redirect there.
  • Preserve existing GitHub and Forgejo repository IDs and sign-in configuration.

Validation

  • Production frontend build and browser checks passed.
  • Isolated integration suites passed against Forgejo 15 and Gitea 1.24.6 with PocketBase 0.40.4, including all three providers together and JSON storage.
  • Real Forgejo/Gitea OAuth tested; GitHub OAuth and model responses use local fixtures. Live installation credentials were not changed.

Setup and limits

Configure each provider under Admin / OAuth, then add repositories in Settings / Repositories. PocketBase is required for sign-in. The included OAuth account migration disables password sign-in and permits accounts without a provider-verified email.

One Forgejo origin and one distinct Gitea origin are supported; URL subpaths are unsupported. Self-hosted re-reviews use the full PR diff plus commit history. GitHub outside-diff caller search is not applied to these repositories.

See the README for setup.