Why does ember-rocks initialize a git repo and commit automatically?

[jonkemp]

My preference would be for ember-rocks to do this optionally and not automatically. Maybe this is something you could prompt the user for using Inquirer.js. What do you think?

[mattma]

@jonkemp The goal of this project follow closely the progress of Ember-CLI but with more sugar syntax, building SaSS product with Node.js backend, gulpjs as a build tool, and more.

In Ember-cli, this is how CLI init a project. It will scaffold a boilerplate and commit them.

What is the use case to make it optionally? Why it is so useful? Thanks.

I saw you have made several gulp-* plugins. If you have free time to contribute this feature, that would be great. I am willing to add more functionalities and it seems Ember-Cli could apply optionally project-name with an existing Ember-Cli project.

My current main priority is Ember-Rocks could automatically take any existing Ember-Cli addons. I think I have a clue how to make it work. It takes some times to implement and test it. Definitely need more help. :)

[jonkemp]

What is the use case to make it optionally? Why it is so useful? Thanks.

It's just not a feature that I want. I find it highly annoying in fact. I understand if you are trying to achieve feature parity with ember-cli however. I too prefer gulp over Broccoli so this tool is intriguing to me. I will think about contributing some code if I have some time. Thanks.

[mattma]

Another reason that I do not have the feature is, I do not think the current file structure (Ember-Rocks) will work with Ember-Cli file structure. So it is not a drop-in replacement for Ember-Cli project. You will most likely scaffold the application Ember rocks way. Otherwise, it won't work correctly.

I think the short workaround is below

# root of Ember-Rocks generated app
rm -rf .git
....
# do whatever the modification you like
git add .
git commit -a -m 'initial commit'

Hope this helps. Contribution is needed. :) Two thumbs up!