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
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -125,12 +125,12 @@ The following options must be configured in order to make a deployment.
125
125
|`branch`| This is the branch you wish to deploy to, for example `gh-pages` or `docs`. |`with`|**Yes**|
126
126
|`folder`| The folder in your repository that you want to deploy. If your build script compiles into a directory named `build` you'd put it here. If you wish to deploy the root directory you can place a `.` here. You can also utilize absolute file paths by appending `~` to your folder path. |`with`|**Yes**|
127
127
128
-
By default the action does not need any token configuration and uses the provided repository scoped GitHub token to make the deployment. If you require most customization you can modify the deployment type using the following options.
128
+
By default the action does not need any token configuration and uses the provided repository scoped GitHub token to make the deployment. If you require more customization you can modify the deployment type using the following options.
|`token`| This option defaults to the repository scoped GitHub Token. However if you need more permissions for things such as deploying to another repository, you can add a Personal Access Token (PAT) here. This should be stored in the `secrets / with` menu **as a secret**. We reccomend using a service account with the least permissions neccersary and recommend when generating a new PAT that you select the least permission scopes neccersary. [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)|`with`|**No**|
133
-
|`ssh-key`| You can configure the action to deploy using SSH by setting this option to a private SSH key stored **as a secret**. It can also
8000
be set to `true` to use an existing SSH client configuration. For more detailed information on how to add your ssh key pair please refer to the [Using a Deploy Key section of this README](https://github.com/JamesIves/github-pages-deploy-action/tree/dev#using-an-ssh-deploy-key-). |`with`|**No**|
133
+
|`ssh-key`| You can configure the action to deploy using SSH by setting this option to a private SSH key stored **as a secret**. It can also be set to `true` to use an existing SSH client configuration. For more detailed information on how to add your public/private ssh key pair please refer to the [Using a Deploy Key section of this README](https://github.com/JamesIves/github-pages-deploy-action/tree/dev#using-an-ssh-deploy-key-). |`with`|**No**|
134
134
135
135
#### Optional Choices
136
136
@@ -199,7 +199,7 @@ jobs:
199
199
runs-on: ubuntu-latest
200
200
steps:
201
201
- name: Checkout ποΈ
202
-
uses: actions/checkout@v2
202
+
uses: actions/checkout@v2.3.1
203
203
204
204
- name: Install and Build π§ # This example project is built using npm and outputs the result to the 'build' folder. Replace with the commands required to build your project, or remove this step entirely if your site is pre-built.
205
205
run: |
@@ -248,7 +248,7 @@ jobs:
248
248
runs-on: windows-latest # The first job utilizes windows-latest
249
249
steps:
250
250
- name: Checkout ποΈ
251
-
uses: actions/checkout@v2
251
+
uses: actions/checkout@v2.3.1
252
252
253
253
- name: Install and Build π§ # This example project is built using npm and outputs the result to the 'build' folder. Replace with the commands required to build your project, or remove this step entirely if your site is pre-built.
254
254
run: |
@@ -266,7 +266,7 @@ jobs:
266
266
runs-on: ubuntu-latest
267
267
steps:
268
268
- name: Checkout ποΈ
269
-
uses: actions/checkout@v2
269
+
uses: actions/checkout@v2.3.1
270
270
271
271
- name: Download Artifacts π» # The built project is downloaded into the 'site' folder.
272
272
uses: actions/download-artifact@v1
@@ -320,7 +320,7 @@ jobs:
320
320
runs-on: ubuntu-latest
321
321
steps:
322
322
- name: Checkout ποΈ
323
-
uses: actions/checkout@v2
323
+
uses: actions/checkout@v2.3.1
324
324
325
325
- name: Install and Build π§ # This example project is built using npm and outputs the result to the 'build' folder. Replace with the commands required to build your project, or remove this step entirely if your site is pre-built.
326
326
run: |
@@ -346,6 +346,6 @@ If you wish to remove these files you must go into the deployment branch directl
346
346
347
347
## Support π
348
348
349
-
This project would not be possible without all of our fantastic [contributors](https://github.com/JamesIves/github-pages-deploy-action/graphs/contributors).
349
+
This project would not be possible without all of our fantastic [contributors](https://github.com/JamesIves/github-pages-deploy-action/graphs/contributors). The project logo was created by [Paganini](https://twitter.com/paganiniart).
350
350
351
351
If you'd like to support the maintenance and upkeep of this project you can [donate via GitHub Sponsors](https://github.com/sponsors/JamesIves). This project is distributed under the [MIT](https://github.com/JamesIves/github-pages-deploy-action/blob/dev/LICENSE) license.
0 commit comments