Closed alex-one-v closed 1 year ago
Hello!
Did sudo apt install git-lfs
resolve the problem?
If not can you please try lfs
with the v4 beta?
on: push
name: π Deploy website on push
jobs:
web-deploy:
name: π Deploy
runs-on: ubuntu-latest
steps:
- name: π Get latest code
uses: actions/checkout@v2.3.2
with:
lfs: true
- name: π Sync files
uses: SamKirkland/FTP-Deploy-Action@beta-v4
with:
server: myFTPserver.com
username: ${{ secrets.FTP_USER }}
password: ${{ secrets.FTP_PASSWORD }}
Hi,
unfortunately sudo apt install git-lfs
didn't help.
v4 beta
works well, thanks you! However it seems it's not based on git-ftp
any more. It doesn't update .git-ftp.log
but uses new .ftp-deploy-sync-state.json
file.
Unfortunately my deploy process is based on git-ftp
, so probably I'll have to continue looking for solution for FTP-Deploy-Action@3.1.1
and LFS
...
Thanks for the help anyway!
I just experienced this too, but it only started happening after a few commits, specifically:
Prior to commit 4 logs said:
Thu Dec 31 21:10:06 UTC 2020: Using syncroot ./ if exists.
Thu Dec 31 21:10:06 UTC 2020: Host is 'ftp.jefulleralerttest.com'.
After it changed to:
Thu Dec 31 21:16:02 UTC 2020: Using syncroot ./ if exists.
git-lfs filter-process: 1: git-lfs filter-process: git-lfs: not found
fatal: the remote end hung up unexpectedly
Thu Dec 31 21:16:02 UTC 2020: Host is 'ftp.jefulleralerttest.com'.
Two commits after adding action did make me π at fetch-depth: 2
, so I tried setting it to fetch-depth: 0
and that worked π
TLDR: set fetch-depth: 0
in actions/checkout@v2
if using lfs: true
Looks like this was an issue with v3 only, v4 appears to work in my tests
Bug Description When I've tired to use the FTP-Deploy-Action with enabled LFS support (by adding lfs: true in the yaml config) git ftp started uploading all the files instead of the new commit only. During the upload process I've got the following error:
And also
Without enabling LFS the FTP-Deploy-Action works OK, and no other issues appeared.
Note: changing fetch-depth: 2 to fetch-depth: 0 not helps. Both errors are still presented. The LFS error is sightly changed
My Action Config
My Action Log