Repositories synced through a GitHub App installation now mirror their Git LFS objects into Code Storage.
Previously, syncing a GitHub App repository brought over Git history and pointer files, but the LFS object bytes always lived on GitHub. Every fetch of a large file had to reach back to GitHub's LFS server. Now, when a repository is synced from a GitHub App installation, its LFS objects are mirrored into Code Storage's managed storage and served directly from there.
Mirroring is lazy. The first time an object is requested it is negotiated against GitHub and copied into Code Storage in the background, so that download still depends on GitHub being reachable. Every subsequent fetch of that object is served directly from Code Storage, with no round trip to GitHub.
There is nothing new to configure. If your repository is already synced through a GitHub App installation and tracks files with LFS, mirroring happens automatically as objects are fetched.
git clone <your-code-storage-remote>
git lfs pullObjects are fetched over the same JWT-authenticated Git remote you already use, with the same
authentication model as every other LFS operation: git:read for fetches and pulls, git:write for
pushes.