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 Init should grab the latest version of the starter without #230

Open
mikeethedude opened this issue Mar 30, 2023 · 1 comment
Assignees
Labels

Comments

@mikeethedude
Copy link
Contributor

mikeethedude commented Mar 30, 2023

Describe the bug
We may have a bug or at least a hiccup in documentation.
emulsify init "theme_name" does not seem to produce the same result as emulsify init "Theme Name" --starter https://github.com/emulsify-ds/emulsify-drupal.git --platform drupal. Passing the repo directly should get the latest tag which I would expect to be equivalent to not passing it when we auto-detect the platform. Some wires may be crossed there.

To Reproduce
Steps to reproduce the behavior:

  1. Set up a new drupal site
  2. `emuslify init "theme_name"
  3. go to the installed theme
  4. Install compound with a branch

Expected behavior
The latest tagged version of emulsify-drupal should be installed when not specifying the repo and drupal is detected.

Desktop (please complete the following information):

  • OS: Ubuntu and MacOs for sure.

Additional context
This was noticed when looking for a specific component from compound that should auto install.

@mikeethedude mikeethedude self-assigned this Mar 30, 2023
@mikeethedude
Copy link
Contributor Author

Coming back to fill this out more.

@amazingrando amazingrando moved this from Incoming to Backlog in Emulsify Project Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Backlog
Development

No branches or pull requests

1 participant