Question

An enterprise administrator reviews the monthly GitHub Enterprise Cloud billing report and notices that Git LFS charges have grown to become the second-largest line item after GitHub Actions. Several teams store large binary build artifacts and machine-learning model files directly in Git LFS, and CI pipelines clone these repositories on every workflow run. The administrator wants to reduce the recurring Git LFS cost while keeping the artifacts available to the teams that need them. Which action most directly addresses the primary Git LFS cost driver shown in the report?

Accepted Answer

Move the large build artifacts and model files out of Git LFS into a dedicated artifact/object store and cache CI dependencies so workflows stop repeatedly pulling LFS objects, reducing both storage and bandwidth consumption

Answer

Enable a repository ruleset that requires signed commits so that large-file pushes are blocked at the branch-protection layer

Answer

Increase the Git LFS data pack allotment on the enterprise account so that the per-gigabyte overage rate no longer applies

Answer

Convert the affected repositories to private visibility, since private repositories do not incur Git LFS bandwidth charges