8000 Update README.md · cauu/github-pages-deploy-action@bb288e9 · GitHub
[go: up one dir, main page]

Skip to content
8000

Commit bb288e9

Browse files
committed
Update README.md
1 parent a8c729a commit bb288e9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ Below you'll find a description of what each option does.
110110
| `BASE_BRANCH` | The base branch of your repository which you'd like to checkout prior to deploying. This defaults to `master`. | `with` | **No** |
111111
| `TARGET_FOLDER` | If you'd like to push the contents of the deployment folder into a specific directory on the deployment branch you can specify it here. | `with` | **No** |
112112
| `CLEAN` | If your project generates hashed files on build you can use this option to automatically delete them from the deployment branch with each deploy. This option can be toggled on by setting it to `true`. | `with` | **No** |
113-
| `CLEAN_EXCLUDE` | If you need to use `CLEAN` but you'd like to preserve certain files or folders you can use this option. This should be formatted as an array string: `CLEAN_EXLUDE: '["filename.js", "./folderpath"]'` | `with` | **No** |
113+
| `CLEAN_EXCLUDE` | If you need to use `CLEAN` but you'd like to preserve certain files or folders you can use this option. This should be formatted as an array but stored as a string. For example: `'["filename.js", "./folderpath"]'` | `with` | **No** |
114114

115115
With the action correctly configured you should see the workflow trigger the deployment under the configured conditions.
116116

0 commit comments

Comments
 (0)
0