Skip to content

Forgejo connection fails to fork if a fork with an unexpected name already exists #7799

Description

@Jak2k

Describe the bug

Login doesn't work if I already have a forgejo fork but with a different name than upstream.

To Reproduce

  1. Fork https://codeberg.org/DI-Day/website/ as diday-website
  2. Sign in at https://diday.org/admin/ using Forgejo
  3. Click "Fork"
  4. See error

Expected behavior

It uses my existing fork as intended.

Screenshots

we need to use a fork on your Forgejo account. (If a fork already exists, we'll use that.) API_ERROR: repository is already forked by user [uname: jak2k, repo path: DI-Day/website, fork path: jak2k/diday-website]

Applicable Versions:

  • Decap CMS version: 3.10.0
  • Git provider: Forgejo
  • OS: FUCKBOI 26.05 (Yarara)
  • Browser version: Firefox 150
  • Node.JS version: -

CMS configuration

https://codeberg.org/DI-Day/website/src/branch/main/public/admin/config.yml

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: bugcode to address defects in shipped code

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions