Git LFS

Code Storage now supports Git LFS on every repository.

Large files can be tracked with the standard git-lfs client and pushed to the same JWT-authenticated Git remote you already use. The LFS endpoint is discovered automatically from the repository URL, so there is no separate server, credential, or client configuration to manage.

git lfs install
git lfs track "*.psd"
git add .gitattributes
git commit -m "track design files with LFS"

git add design.psd
git commit -m "add design asset"
git push origin main

Git history stores the pointer files while Code Storage stores the object bytes in managed S3. LFS uploads use the same authentication model as Git operations: git:read for fetches and pulls, git:write for pushes.

Repository deletion also cleans up the repository's LFS objects, keeping object lifecycle tied to the repo that owns them.

See the docs ->