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: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,7 +132,6 @@ By default, the action does not need any token configuration and uses the provid
132
132
| `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** |
133
133
| `force` | Force-push new deployments to overwrite the previous version; otherwise, attempt to rebase new deployments onto any existing ones. This option is turned on by default and can be toggled off by setting it to `false`, which may be useful if there are multiple deployments in a single branch. | `with` | **No** |
134
134
| `silent` | Silences the action output preventing it from displaying git messages. | `with` | **No** |
135
-
| `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** |
136
135
| `tag` | Add a tag to the commit. Only works when `dry-run` is not used. | `with` | **No** |
137
136
138
137
With the action correctly configured you should see the workflow trigger the deployment under the configured conditions.
Copy file name to clipboardExpand all lines: action.yml
+2-6Lines changed: 2 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ inputs:
24
24
However if you need more permissions for things such as deploying to another repository, you can add a Personal Access Token (PAT) here.
25
25
This should be stored in the `secrets / with` menu **as a secret**.
26
26
27
-
We recommend using a service account with the least permissions neccersary
27
+
We recommend using a service account with the least permissions necessary
28
28
and when generating a new PAT that you select the least permission scopes required.
29
29
30
30
[Learn more about creating and using encrypted secrets here.](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)
@@ -58,7 +58,7 @@ inputs:
58
58
required: false
59
59
60
60
dry-run:
61
-
description: 'Do not actually push back, but use `--dry-run` on `git push` invocations insead.'
61
+
description: 'Do not actually push back, but use `--dry-run` on `git push` invocations instead.'
62
62
required: false
63
63
64
64
force:
@@ -78,10 +78,6 @@ inputs:
78
78
description: 'Allows you to specify a different repository path so long as you have permissions to push to it. This should be formatted like so: JamesIves/github-pages-deploy-action'
79
79
required: false
80
80
81
-
workspace:
82
-
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."
83
-
required: false
84
-
85
81
tag:
86
82
description: "Add a tag to the commit, this can be used like so: 'v0.1'. Only works when 'dry-run' is not used."
0 commit comments