I want to enable Git LFS for a certain file type repo-wide, but disable it in selected subfolders, i.e., accomplish a modular management of LFS in a Git repo.

Is it possible to have multiple Git LFS repo for a single Git Repo?

When using following .gitattributes, does it also track any folder named “models” regardless its location within the project?

It seems that if you try to clone & checkout a git repository which makes use of git-lfs, while the current machine doesn’t have git-lfs installed, it simply ‘works’ without any errors or warnings, but ‘does the wrong thing’ (by checking out ‘pointer’ files instead of what they point to, if they’re being managed by git-lfs)

Imagine a repo with the following history

We are using Git LFS to store .png files in our GitLab repository. However, there is a possibility a commit will contain a raw .png file instead of a Git LFS pointer file. (For example, someone might not have Git LFS installed and push a raw file to the repo, or they might commit & push without git hooks). If neither the author nor the reviewee notices & the file ends up in the main branch, the image will end up permanently hogging up space in the history of the repo.

How can I exclude Git LFS files from being pulled during a clone?

I am using curl command with private token and url to download a file from directory.
For example such way:

So I want to store my large files locally on a backup harddrive instead of pushing them and storing them to a remote server. I basically want that backup harddrive to act as the remote server.

I am really stuck with git lfs. This is the first time I was trying to use it. I was on a feature branch. I ran [1]: