decaporg / decaporg/decap-cms

Cannot use when fork name differs from upstream repo name

Open
#7,344 2 comments 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**

When your github fork has a different name than upstream repo, you cannot use decapcms.

**To Reproduce**

I'm using github backend with open authoring in https://github.com/OCA/docs

This repo was before named https://github.com/moduon/oca-docs while it was a prototype. Some users already tested the prototype with Decap CMS and [they had forks](https://github.com/OCA/docs/forks) named `oca-docs` because of that:
![image](https://github.com/user-attachments/assets/df5ee01d-dfb6-47e1-980b-861d4a4d755d)

Now, when these users try to [use decap-cms in the new site](https://oca-docs.netlify.app/admin/), they cannot because their fork isn't named `docs` but `oca-docs`.

**Expected behavior**

They can use open authoring

**Screenshots**

Do login. The, click on fork:
![image](https://github.com/user-attachments/assets/dce143d1-02aa-47e6-871e-67491d2a9850)

Then, the error:
![image](https://github.com/user-attachments/assets/12ee5e10-70d4-474b-92ef-79395f88b20a)

**Applicable Versions:**

- Decap CMS version: 3.0.0
- Git provider: GitHub
- OS: Ubuntu
- Browser version: Chrome.

**CMS configuration**

https://github.com/OCA/docs/blob/b79cd4097f188f19a4182bf6ec203e4c6d104eef/static/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.