Actions/FTP-Deploy-Action
1
Fork 0
mirror of https://github.com/SamKirkland/FTP-Deploy-Action.git synced 2025-11-04 01:33:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update fetch-depth to 0

Browse Source 
There's a chance I'm misunderstanding this, but setting the fetch-depth to 2 will cause a comparison of only the last 2 commits on deploy. If you have made more than 2 commits since the last deployment the comparison fails and all files are uploaded again. With even relatively small projects this could make the deployment time go up significantly.

Setting the fetch-depth to 0 will cause it to look back over all commits to determine the delta of files to upload and reduce the FTP time significantly over uploading from scratch. See https://github.com/SamKirkland/FTP-Deploy-Action/issues/82 and possibly https://github.com/SamKirkland/FTP-Deploy-Action/issues/78

Also see the docs related to fetch-depth: https://github.com/actions/checkout#checkout-v2
This commit is contained in:
tflight 2020-07-17 11:10:13 -04:00 committed by GitHub
parent 79e6bdd312
commit 3e4bf97068
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -21,7 +21,7 @@ jobs:
steps: steps:
- uses: actions/checkout@v2.1.0 - uses: actions/checkout@v2.1.0
with: with:
fetch-depth: 2 fetch-depth: 0
- name: FTP-Deploy-Action - name: FTP-Deploy-Action
uses: SamKirkland/FTP-Deploy-Action@3.1.1 uses: SamKirkland/FTP-Deploy-Action@3.1.1
with: with:
@ -181,7 +181,7 @@ jobs:
steps: steps:
- uses: actions/checkout@v2.1.0 - uses: actions/checkout@v2.1.0
with: with:
fetch-depth: 2 fetch-depth: 0
- name: FTP-Deploy-Action - name: FTP-Deploy-Action
uses: SamKirkland/FTP-Deploy-Action@3.1.1 uses: SamKirkland/FTP-Deploy-Action@3.1.1
with: with:
@ -209,7 +209,7 @@ jobs:
steps: steps:
- uses: actions/checkout@v2.1.0 - uses: actions/checkout@v2.1.0
with: with:
fetch-depth: 2 fetch-depth: 0
- name: FTP-Deploy-Action - name: FTP-Deploy-Action
uses: SamKirkland/FTP-Deploy-Action@3.1.1 uses: SamKirkland/FTP-Deploy-Action@3.1.1
@ -256,7 +256,7 @@ jobs:
steps: steps:
- uses: actions/checkout@v2.1.0 - uses: actions/checkout@v2.1.0
with: with:
fetch-depth: 2 fetch-depth: 0
- name: FTP-Deploy-Action - name: FTP-Deploy-Action
uses: SamKirkland/FTP-Deploy-Action@3.1.1 uses: SamKirkland/FTP-Deploy-Action@3.1.1
@ -284,7 +284,7 @@ jobs:
steps: steps:
- uses: actions/checkout@v2.1.0 - uses: actions/checkout@v2.1.0
with: with:
fetch-depth: 2 fetch-depth: 0
- name: Use Node.js 12.x - name: Use Node.js 12.x
uses: actions/setup-node@v1 uses: actions/setup-node@v1
@ -320,7 +320,7 @@ jobs:
steps: steps:
- uses: actions/checkout@v2.1.0 - uses: actions/checkout@v2.1.0
with: with:
fetch-depth: 2 fetch-depth: 0
- name: FTP-Deploy-Action - name: FTP-Deploy-Action
uses: SamKirkland/FTP-Deploy-Action@3.1.1 uses: SamKirkland/FTP-Deploy-Action@3.1.1
@ -347,9 +347,7 @@ See the [`.git-ftp-ignore`](#ignore-specific-files-when-deploying) example secti
By default only different files are uploaded. By default only different files are uploaded.
Verify you have `with: fetch-depth: 2` in your `actions/checkout@v2.1.0` step. The last 2 checkins are required in order to determine differences Verify you have `with: fetch-depth: 0` in your `actions/checkout@v2.1.0` step. Setting this to `0` allows all commits to be retrieved in order to determine the changed files. You can set this to another number (e.g. 2) however only that many commits will be used for the comparison. If you have made more commits than that since the last deploy, all files will be uploaded to get back in sync.
If you've had multiple git commits without deploying, all files will be uploaded to get back in sync
Verify you **don't** have the `--all` git-ftp-args flag set Verify you **don't** have the `--all` git-ftp-args flag set
</details> </details>