decaporg / decaporg/decap-cms

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

Open
#7,799 1 comment 0 reactions 0 assignees View on GitHub
type: bug
Dominant language
JavaScript
Stars
19.4k
Forks
3.1k
Avg merge
1d 14h
Merged PRs (30d)
9

Description

**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**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.