Open CEbbinghaus opened 4 years ago
For our project this is major issue, since when checking out to an empty workspace, .lfsconfig file does not yet exist and lfs fetch then fails to find the files (since it looks them from the wrong server). However, we just stopped using lfs: true and we do git lfs pull after checkout.
This is a major problem for us. Would a contribution to fix this be welcome?
I was suprised to run into this issue. I found a workout if you remove:
with:
lfs: true
Then add a second step:
- name: Checkout LFS
run: git lfs fetch --all && git lfs checkout
Possible just git lfs pull
would suffice. I found this respects the .lfsconfig
file (it worked for my action). I'm guessing it'd also respect the .git/config
[lfs]
config if that were edited inside the action runner.
I orignally added sudo apt install -y git-lfs
but it was already installed.
When Cloning a Repository that uses a third party lfs server it still tries to pull from github's lfs
Action:
.lfsconfig:
output:
It would be nice if either a Settings for the
lfs-url
were to be exposed or it would simply read the .lfsconfig file and use the provided one. 👍