If we want to make it easy to merge an upstream repo (such as this one), from another Mojito container, users will constantly run into merge conflicts for commonly shared files such as:
config.js
shared-code.js
This makes it harder to merge because you have to mange the conflicts on these particular files.
Instead, what if we renamed these files to:
config.js.example
shared-code.js.example
And upon first run of gulp scripts, if config.js or shared-code.js files do not exist, we create them.
If we want to make it easy to merge an upstream repo (such as this one), from another Mojito container, users will constantly run into merge conflicts for commonly shared files such as:
config.jsshared-code.jsThis makes it harder to merge because you have to mange the conflicts on these particular files.
Instead, what if we renamed these files to:
config.js.exampleshared-code.js.exampleAnd upon first run of
gulp scripts, ifconfig.jsorshared-code.jsfiles do not exist, we create them.