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
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,6 @@ In addition to the deployment options you must also configure the following.
147
147
|`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**|
148
148
|`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**|
149
149
|`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 neccersary to set this variable if you're using the node module. |`with`|**No**|
150
-
|`DEBUG`| By default the git commands are hidden from the log. If you'd like to turn them on you can toggle this to `true`. **If you're using this action in your own project as a node module via yarn or npm you may expose your secrets if you toggle this on in a production environment**. |`with`|**No**|
151
150
152
151
With the action correctly configured you should see the workflow trigger the deployment under the configured conditions.
153
152
@@ -305,3 +304,9 @@ If you use a [container](https://help.github.com/en/actions/automating-your-work
305
304
### Additional Build Files 📁
306
305
307
306
This action maintains the full git history of the deployment branch. Therefore if you're using a custom domain and require a `CNAME` file, or if you require the use of a `.nojekyll` file, you can safely commit these files directly into deployment branch without them being overridden after each deployment.
307
+
308
+
### Debugging 🐝
309
+
310
+
By default the git commands are hidden from the logs. If you'd like to turn them on you can set the `ACTIONS_RUNNER_DEBUG` environment variable within the `Settings/Secrets` menu.
311
+
312
+
If you're using this action in your own project as a node module via yarn or npm you'll need to set `RUNNER_DEBUG` as the environment variable instead. **You may expose your secrets if you toggle this on in a production environment**. You can learn more about debugging GitHub actions [here](https://github.com/actions/toolkit/blob/master/docs/action-debugging.md).
Copy file name to clipboardExpand all lines: action.yml
-4Lines changed: 0 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,3 @@ inputs:
63
63
WORKSPACE:
64
64
description: "This should point to where your project lives on the virtual machine. The GitHub Actions environment will set this for you. It is only neccersary to set this variable if you're using the node module."
65
65
required: false
66
-
67
-
DEBUG:
68
-
description: "By default the git commands are hidden from the log. If you'd like to turn them on you can toggle this to true."
0 commit comments