CMS defaults to master branch even when repository uses main , causing API‑ERROR: Branch not found
CMS defaults to master branch even when repository uses main , causing API‑ERROR: Branch not found: a task in LegoFlow-SWE (Harbor dataset). When a user does not explicitly configure a branch in their admin/config.yml , the CMS backend automatically assumes the branch name is master . Many…
The task
When a user does **not** explicitly configure a `branch` in their `admin/config.yml`, the CMS backend automatically assumes the branch name is `master`. Many repository hosts (GitHub, GitLab, Bitbucket) now default to `main` instead, so publishing content will fail with an `API_ERROR: Branch not found` error unless…
Part of Lego-X/LegoFlow-SWE.