Limitations

This page lists what repository mirrors do not support yet, with workarounds where they exist.

Git LFS

Mirrors do not currently support Git LFS. Cloning a mirror of a repository that uses LFS fails during checkout, because Git LFS tries to download the large files through the entire:// remote:

Error downloading object: ... batch request: ssh: Could not resolve hostname entire
error: external filter 'git-lfs filter-process' failed
fatal: <file>: smudge filter lfs failed

Workaround

Point Git LFS at GitHub so that all large file transfers go through GitHub, while regular Git operations keep using the mirror. For a fresh clone, skip LFS downloads during checkout, set the LFS URL, then pull the LFS files:

GIT_LFS_SKIP_SMUDGE=1 git clone entire://aws-us-east-2.entire.io/gh/<owner>/<repo>
cd <repo>
git config lfs.url "https://github.com/<owner>/<repo>.git/info/lfs"
git lfs pull

For an existing checkout, set the LFS URL and pull:

git config lfs.url "https://github.com/<owner>/<repo>.git/info/lfs"
git lfs pull

Continue With

Mirrors

Learn how mirrors make GitHub repositories available in Entire.

Troubleshooting

Fix mirror setup, access, clone, fetch, and push issues.

⌘I

Getting Started

Platforms

Guides

Security

Resources

Git LFS

Workaround

Continue With

Mirrors

Troubleshooting

​Git LFS

​Workaround

​Continue With

Mirrors

Troubleshooting

Git LFS

Workaround

Continue With