The git lfs pull command is not handled by gitcache, as it was not necessary with previous versions of git-lfs. However, the
behaviour of git-lfs has changed and leads to errors when the remote (fetch URL) is set to the mirror. When the remote fetch URL is set to the remote repository, git lfs pull works as expected. This happens only if there are files to fetch, e.g., files that are filtered by default but are included using the command line options --include and --exclude "".
So the git lfs pull commands should be handled by gitcache in the following way:
If the specified remote is not origin, proceed with the original git command.
Change the remote fetch URL to the push URL.
Perform the original git command.
Restore the remote fetch URL.
An alternative would be to setup a temporary remote like real-origin and use that remote. This would have the advantage of being more robust in cases where the command is interrupted and leaving the temporary fetch URL.
seeraven
commented
2 years ago
The
git lfs pullcommand is not handled by gitcache, as it was not necessary with previous versions of git-lfs. However, the behaviour of git-lfs has changed and leads to errors when the remote (fetch URL) is set to the mirror. When the remote fetch URL is set to the remote repository,git lfs pullworks as expected. This happens only if there are files to fetch, e.g., files that are filtered by default but are included using the command line options--includeand--exclude "".So the
git lfs pullcommands should be handled by gitcache in the following way:origin, proceed with the original git command.An alternative would be to setup a temporary remote like
real-originand use that remote. This would have the advantage of being more robust in cases where the command is interrupted and leaving the temporary fetch URL.