Description
We have the ability to ignore more files when deploying in order to prevent certain configuration files and source files from ever making it to production, and we should take advantage of that more than we currently are. Modify the .deployignore file in the root of the create-wordpress-project repo so that it ignores the following files and folders:
In the root:
- .github
- .editorconfig
- .eslintrc.js
- .npmrc
- .nvmrc
- .phpcs.xml
- .stylelintrc.json
- .turbo
- composer.json
- composer.lock
- custom.d.ts
- jest.config.ts
- package.json
- package-lock.json
- phpstan.neon
- README.md
- tsconfig.json
- turbo.json
In the plugin (set the start of the path to plugins/create-wordpress-plugin):
- .scaffolder
- blocks
- config/README.md
- entries
- scaffold
- tests
- .eslintignore
- .phpcs.xml
- .stylelintignore
- babel.config.js
- jsconfig.json
- package.json
- phpunit.xml
In the theme (set the start of the path to themes/create-wordpress-theme):
- assets
- entries
- tests
- .eslintignore
- .phpcs.xml
- .stylelintignore
- babel.config.js
- jsconfig.json
- package.json
- phpunit.xml
- webpack.config.js
Use Case
When a user uses this package, they should only be deploying the necessary files to production and nothing else.
Description
We have the ability to ignore more files when deploying in order to prevent certain configuration files and source files from ever making it to production, and we should take advantage of that more than we currently are. Modify the
.deployignorefile in the root of thecreate-wordpress-projectrepo so that it ignores the following files and folders:In the root:
In the plugin (set the start of the path to
plugins/create-wordpress-plugin):In the theme (set the start of the path to
themes/create-wordpress-theme):Use Case
When a user uses this package, they should only be deploying the necessary files to production and nothing else.