Need intuition on checking in a large file in git repository

[Musab Shakeel]

If someone wanted to check in a large (11 MB) text file into a git repository served by Gerrit that had heavy human + CI traffic (clone / fetch / push), how strongly would I want to push for using LFS instead of checking the file into the git repo? 

The file: https://github.com/googleapis/google-cloud-go/blob/main/compute/apiv1/computepb/compute.pb.go

The file won't be modified by anyone, would just be required for builds in CI workspace (Jenkins). 

[Nasser Grainawi]

On Thu, Apr 3, 2025 at 8:20 AM 'Musab Shakeel' via Repo and Gerrit Discussion <repo-d...@googlegroups.com> wrote:

If someone wanted to check in a large (11 MB) text file into a git repository served by Gerrit that had heavy human + CI traffic (clone / fetch / push), how strongly would I want to push for using LFS instead of checking the file into the git repo? 

I wouldn't worry about LFS for this. That seems like reasonably compressible text content.

 

The file: https://github.com/googleapis/google-cloud-go/blob/main/compute/apiv1/computepb/compute.pb.go

The file won't be modified by anyone, would just be required for builds in CI workspace (Jenkins). 

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/repo-discuss/9e0272f6-21a7-4790-b7ba-e078d3d0b741n%40googlegroups.com.