Allow for project specific .gitignore to follow through deployment process?

[AaronHolbrook]

Currently the deploy strips out the project's gitignore and adds it's own. This is to ensure that we are tracking appropriate dependencies and we are not overwriting wp core files or the uploads dir.

Should we be worried about specific project files though?

@philipnewcomer @jacobarriola @cjkoepke

[cjkoepke]

I'm not sure if you're ignoring .sass-cache but that is usually pretty large and should be ignored.

[AaronHolbrook]

does that get added normally?

[AaronHolbrook]

I don't see a sass-cache folder:

[philipnewcomer]

.sass-cache (along with node_modules and other dependencies/temporary files) should not be committed to version control.

[AaronHolbrook]

Added

[cjkoepke]

I think it depends on the sass package we use, but I know that ruby-sass adds that. Would be good to catch so probably good that you added it just in case.

[philipnewcomer]

composer.json has credentials to the Zeeklabs wpp packagist and shouldn't be deployed