You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,6 +151,7 @@ In addition to the deployment options you must also configure the following.
151
151
|`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", "folder"]'`|`with`|**No**|
152
152
|`SINGLE_COMMIT`| This option can be toggled to `true` if you'd prefer to have a single commit on the deployment branch instead of maintaining the full history. **Using this option will also cause any existing history to be wiped from the deployment branch**. |`with`|**No**|
153
153
|`LFS`| If toggled all files will be migrated from [Git LFS](https://git-lfs.github.com/) so they can be comitted to the deployment branch. |`with`|**No**|
154
+
|`PRESERVE`| Preserves and restores the workspace prior to deployment. This option is useful if you're modifying files in the worktree that aren't comitted to Git. |`with`|**No**|
154
155
|`SILENT`| Silences the action output preventing it from displaying git messages. |`with`|**No**|
155
156
|`WORKSPACE`| This should point to where your project lives on the virtual machine. The GitHub Actions environment will set this for you. It is only necessary to set this variable if you're using the node module. |`with`|**No**|
0 commit comments