Correct me if I'm wrong, but it's not enough to delete the files in the commit, unless you're ok with Git tracking the large amount of data that was previously committed. Your git clones will be long, my friend

[–] Shareni@programming.dev 0 points 2 years ago (1 children)

git clone --depth=1 ?

[–] flying_sheep@lemmy.ml 0 points 2 years ago (1 children)

No, don't do that. That modifies the commit hashes, so tags no longer work.

git clone --filter=blob:none is where it's at.

[–] masterspace@lemmy.ca -1 points 2 years ago* (last edited 2 years ago)

I don't understand how we're all using git and it's not just some backend utility that we all use a sane wrapper for instead.

Everytime you want to do anything with git it's a weird series or arcane nonsense commands and then someone cuts in saying "oh yeah but that will destroy x y and z, you have to use this other arcane nonsense command that also sounds nothing like you're trying to do" and you sit there having no idea why either of them even kind of accomplish what you want.

[–] xmunk@sh.itjust.works 1 points 2 years ago (1 children)

You already stopped Steven in a prior commit.

Also, if this is an organization setting, I'm extremely disappointed in your PR review process. If someone is committing vendor code to the repo someone else should reject the pull.

[–] Cqrd@lemmy.dbzer0.com 1 points 2 years ago

What if I told you a lot of companies don't have solid review requirement processes? Some barely use version control at all