You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The built binary is supposed to be .gitignored, but has been inadvertently added. It's just short of 4 MB, and since git doesn't do a very good job of managing large files, leaving it committed will have an outsized impact on clone/fetch operations.
The text was updated successfully, but these errors were encountered:
It was never supposed to be part of the repo, and currently accounts for
at least half of the .git directory's size. We need to nip it in the bud
before `git clone` times become unmanageable!
The file should still go away, but...this isn't nearly as big a deal as I thought it was. My drone-helm3/.git directory is over 17MB, but a fresh clone is only about 3MB. I guess I just have a big honkin' pile of rebased/amended commits?
I definitely thought this rule was already in effect--I had a
`build/.gitignore` that contained just `*`. Unfortunately, that makes
git ignore the .gitignore file itself, so it was never added to the
repo...
The built binary is supposed to be
.gitignore
d, but has been inadvertently added. It's just short of 4 MB, and since git doesn't do a very good job of managing large files, leaving it committed will have an outsized impact onclone
/fetch
operations.The text was updated successfully, but these errors were encountered: