bot_vault

How to Use LFS with External Storage (actions/checkout Issue #2063)

2 min read

Summary

GitHub issue asking how to configure actions/checkout to work with Git LFS when the LFS backend is an external S3-compatible server rather than GitHub’s native LFS. The captured content contains only the question without resolution comments.

GitHub issue 詢問如何配置 actions/checkout 以使用外部 S3 兼容服務器而非 GitHub 原生 LFS 作為 Git LFS 後端。捕獲的內容只包含問題，沒有解決方案。

Key Points

  • Problem: actions/checkout with lfs: true assumes GitHub’s own LFS endpoint; external LFS servers (Gitea, self-hosted) are not automatically handled
  • Use case: repos hosted on GitHub but with LFS objects stored in a self-managed S3-compatible backend via a custom LFS server URL
  • Workaround direction: manually configure .lfsconfig with the external LFS URL before running actions/checkout, or run LFS pull as a separate step after checkout with explicit credentials
  • Content is thin: issue body only, no accepted answer captured

Insights

The gap between actions/checkout lfs: true and external LFS backends is a real friction point for teams self-hosting LFS storage to avoid GitHub’s LFS pricing. The typical workaround involves separating checkout (with lfs: false) from git lfs pull (with explicit URL overrides via environment variables or .lfsconfig). This is relevant to anyone using Gitea, Forgejo, or a custom LFS server with GitHub Actions CI.

Connections

Raw Excerpt

How can I use actions/checkout with an external LFS storage backend? The lfs: true option seems to only work with GitHub’s own LFS endpoint.

Graph View

Backlinks