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

[BUG] emulsify-cli assumes that a custom starter theme's default branch is 'master' #280

Open
calebtr-metro opened this issue Jun 21, 2024 · 0 comments
Labels

Comments

@calebtr-metro
Copy link
Collaborator

Describe the bug
emulsify-cli assumes that a custom starter theme's default branch is 'master'.

The error is:

fatal: Remote branch master not found in upstream origin

However if you specify a --checkout, then starter theme is installed correctly.

To Reproduce
Steps to reproduce the behavior:

  1. Initialize a project with a custom starter theme repository where the default branch is not "master"; verify that it is valid by specifying a checkout on the command line:

    emulsify init -p drupal --starter [email protected]:calebtr-metro/emulsify-starter-demonstration.git --checkout main . test-success

  2. Initialize a project with the same repository but leave out the --checkout flag:

    emulsify init -p drupal --starter [email protected]:calebtr-metro/emulsify-starter-demonstration.git . test-fail

  3. See error.

fatal: Remote branch master not found in upstream origin

Expected behavior
emulsify-cli should identify a repository's correct default branch / HEAD.

Additional context

  • node v20.11.1
  • emulsify v1.9.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Incoming
Development

No branches or pull requests

1 participant