-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Broken Netlify CMS due to Github master branch name change to "main" #4417
Comments
You'll have to set a branch manually if you want to use something else than master:
|
@tomrutgers I realize that, but I figured it may be good to add logic to handle this change in Githubs default naming conventions |
I see, thanks for clarifying! |
Could this be added to the default github config code block in the docs? 🙏 I appreciate the available options are outlined in the account settings overview but with main being the default branch name in github now, many people who go straight to the github How To will end up with errors. |
Hi @stephlocke, would you mind submitting a PR for it? You can do it by clicking |
👍 #5264 |
Closing as stale and/or outdated. |
When a branch is not specified in config.yml, Netlify defaults to using master branch of repo. Due to recent name change of master branch to main , this creates an API_ERROR: cannot find branch in CMS when publishing entries and 404 errors on initial CMS load.
To Reproduce
netlify-cms-app
. I used gatsby.js for my project.Expected behavior
Initial load of localhost:8000/admin results in 404 (that are handled well). Main problem is introduced when publishing CMS entries. API_ERROR occurs.
Applicable Versions:
CMS configuration
The text was updated successfully, but these errors were encountered: