5 ms·

What if that's only you? Git isn't made only for those who "just want to install something"

• snthpy 5mo ago
  Fair enough. I also work with a monorepo at work but that I cloned like 5 years ago. If I think about what I've cloned over the last week or so (LazyVim, gstack, my dotfiles), most of the time I just want the current state and be able to pull updates. Even for my dotfiles or projects that I fork and hack on, most of the time I'm just adding commits and it's seldom that I want to go back to historical ones. Given how often I see `git clone ...` instructions in Github README.md files, I was just wondering how many other people felt the same? So my contention is that most of the time, `git clone --depth 1` or `git clone --filter=blob:none` is what you actually want, and in the case that you want the full history then you could do `git clone --depth 0` (or `git clone -full` for even better UX, not that the git cli is known for it's UX).