Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot use when fork name differs from upstream repo name #7344

Open
yajo opened this issue Dec 9, 2024 · 0 comments
Open

Cannot use when fork name differs from upstream repo name #7344

yajo opened this issue Dec 9, 2024 · 0 comments
Labels
type: bug code to address defects in shipped code

Comments

@yajo
Copy link

yajo commented Dec 9, 2024

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 named oca-docs because of that:
image

Now, when these users try to use decap-cms in the new site, 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

Then, the error:
image

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

@yajo yajo added the type: bug code to address defects in shipped code label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug code to address defects in shipped code
Projects
None yet
Development

No branches or pull requests

1 participant