TypeError: Cannot read properties of undefined (reading 'path')

Describe the bug

To Reproduce

Expected behavior

Screenshots

Applicable Versions:

• Netlify CMS version: netlify-cms@2.10.164
• Git provider: github
• Browser version: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.63 Safari/537.36

CMS configuration

backend:
  name: github
  repo: ux-at-icfnext/practice-netlify-cms
  "netlify.configure({'site_id'": gifted-boyd-d36ba9.netlify.com});
media_folder: assets/img/uploads
collections:
  - label: Posts
    name: posts
    folder: _posts
    create: true
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    fields:
      - label: Layout
        name: layout
        widget: hidden
        default: default
      - label: Title
        name: title
        widget: string
      - label: Description
        name: desc
        widget: string
      - label: Body
        name: body
        widget: markdown
    publish: true
    type: folder_based_collection
    sortable_fields:
      - commit_date
      - title
      - commit_author
    view_filters: []
    view_groups: []
publish_mode: simple
slug:
  encoding: unicode
  clean_accents: false
  sanitize_replacement: "-"
public_folder: /assets/img/uploads
isFetching: false
error: null

Additional context

[bytrangle]

@gangsthub : The issue will always get resolved if you specify the branch name in the config. Actually, it only manifests when you don’t configure branch name, which I think is the case with many newly-initiated project with Netlify CMS.

What happens under the hood is that Netlify CMS will assume that your default branch is master, which is no longer the case with all the major Git host. Then, when it tried to push content to master branch, it will get hit with an 404 (IIRC) error because master doesn’t exist in many repos.

So, that’s the gist of the problem 😓.

[bytrangle]

@gangsthub Many of us got tripped by that when first setting up Netlify CMS 😃.