-
-
Notifications
You must be signed in to change notification settings - Fork 25
Description
The tool is great for react beginners (like me), but it can also cause lots of confusion when used in a subdirectory of an already existing git repo.
When I took the Pluralsight course "React: Getting Started", I of course wanted the first experiment with reactful to live in a subdirectory of my private repository where I kept all my experiments from the course. This caused the weird situation that I now somehow "had" a git submodule (in the sense that I could not git add the generated files to my enclosing repo), but somehow I had not, because it was not a proper submodule. There was no .gitmodule and .git/modules/. So I ended up setting up everything from scratch to recover.
This could have been avoided easily by dropping the dangerous git init default from the procedure. When I want it, it's just one command, but when I don't want for some reason may be big effort to get rid of it. And the course gave no hint and neither gives the README.md. And, well, who spoofs the code to find this here before following the advice from the course... ;)
Line 48 in 500f05a
| .option('--no-git', 'Skip initializing the app as a git repo') |