mirror of
https://github.com/JamesIves/github-pages-deploy-action.git
synced 2023-12-15 20:03:39 +08:00
Update README.md
This commit is contained in:
parent
2e04082037
commit
de07b5b8c6
12
README.md
12
README.md
@ -75,12 +75,6 @@ With the action correctly configured you should see the workflow trigger the dep
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
### Additional Build Files 📁
|
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
### Using an SSH Deploy Key 🔑
|
### Using an SSH Deploy Key 🔑
|
||||||
|
|
||||||
If you'd prefer to use an SSH deploy key as opposed to a token you must first generate a new SSH key by running the following terminal command, replacing the email with one connected to your GitHub account.
|
If you'd prefer to use an SSH deploy key as opposed to a token you must first generate a new SSH key by running the following terminal command, replacing the email with one connected to your GitHub account.
|
||||||
@ -226,3 +220,9 @@ If you use a [container](https://help.github.com/en/actions/automating-your-work
|
|||||||
- name: Deploy
|
- name: Deploy
|
||||||
uses: JamesIves/github-pages-deploy-action@releases/v3
|
uses: JamesIves/github-pages-deploy-action@releases/v3
|
||||||
```
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### Additional Build Files 📁
|
||||||
|
|
||||||
|
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.
|
||||||
|
Loading…
Reference in New Issue
Block a user