Fix CMS publication branch - #922
Open
gellowg wants to merge 2 commits into
Open
Conversation
cssbhamdev
enabled auto-merge (squash)
August 21, 2026 19:55
github-actions
Bot
added
the
sync
|
This pull request has been marked to automatically sync to its base branch. You can disable this behavior by removing the label. |
Member
|
Just to note the default way historically to log in to Netlify is to login with github and the cssbhamdev account - so if you're logging in with something else that probably also isn't helping |
Contributor
Author
Thank you for letting me know, that makes a lot more sense in terms of getting OAuth access. I will use the cssbhamdev account instead. I think the configuration still needs to be changed to from master to main to get it to work though. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
At the moment the Netflify CMS doesn't let authenticated users view, edit or delete any of the publications. This is because the backend configuration uses the
masterbranch, rather than themainbranch we have. There is nomasterbranch. I suspect at some point the branch was renamed frommastertomain, butadmin/config.ymlwas never updated. The CMS was therefore attempting to persist entries to a branch that no longer exists.I have changed the CMS publication branch from
mastertomain.