We shrunk our Javascript monorepo git size
jonathancreamer.com
We shrunk our Javascript monorepo git size
1–10 of 226 posts
Re: We shrunk our Javascript monorepo git size
#2> Retroactively, once the file is there though, it's semi stuck in history.
Arguably, the fix for that is to run filter-branch, remove the offending binary, teach and get everyone setup to use git-lfs for binaries, force push, and help everyone get their workstation to a good place.
Far from ideal, but better than having a large not-even-used file in git.
Re: We shrunk our Javascript monorepo git size
#3> Large blobs happens when someone accidentally checks in some binary, so, not much you can do > Retroactively, once the file is there though, it's semi stuck in history. Arguably, the fix for that is to run filter-branch, remove the offending binary, teach and get everyone setup to use git-lfs for binaries, force push, and help everyone get their workstation to a good place. Far from ideal, but better than having a…
Re: We shrunk our Javascript monorepo git size
#4Re: We shrunk our Javascript monorepo git size
#5Shrank
Re: We shrunk our Javascript monorepo git size
#6Shrank
Re: We shrunk our Javascript monorepo git size
#7The explanation probably got lost among all the gifs, but the last 16 chars here are different:
> was actually only checking the last 16 characters of a filename > For example, if you changed repo/packages/foo/CHANGELOG.md, when git was getting ready to do the push, it was generating a diff against repo/packages/bar/CHANGELOG.md!
Re: We shrunk our Javascript monorepo git size
#8Re: We shrunk our Javascript monorepo git size
#9What is it about Europe that makes it more difficult? That internet in Europe isn't as good? Actually, I have heard that some primary schools in Europe lack internet. My grandson's elementary school in rural California (population <10k) had internet as far back as 1998.
Re: We shrunk our Javascript monorepo git size
#10What's up with folks in Europe that they can't clone a big repo, but others can? Also it sounds like they still won't be able to clone, until the change is implemented on the server side?
> This meant we were in many occasions just pushing the entire file again and again, which could be 10s of MBs per file in some cases, and you can imagine in a repo
The sentence seems to be cut off.
Also, the gifs are incredibly distracting while trying to read the article, and they are there even in reader mode.