GIT-LFS-FILTER-PROCESS(1)

🎀 NAME 🎀

okay so bestie, this is git-lfs-filter-process(1): the Git filter process that converts between pointer and actual content. slay 💅

✨ SYNOPSIS ✨

git lfs filter-process
git lfs filter-process --skip

🦋 DESCRIPTION 🦋

okay so picture this: filter-process implements the Git process filter API. it exchanges handshake messages, then accepts and responds to requests to either clean or smudge a file. iconic behavior, honestly ✨

filter-process is always run by Git’s filter process, and it’s configured by the repository’s Git attributes. no cap.

In your Git configuration or in a .lfsconfig file, you may set either or both of lfs.fetchinclude and lfs.fetchexclude to comma-separated lists of paths. here’s the vibe:

• If lfs.fetchinclude is defined, Git LFS pointer files will only be replaced with the contents of the corresponding Git LFS object file if their path matches one in that list.
• If lfs.fetchexclude is defined, Git LFS pointer files will only be replaced with the contents of the corresponding Git LFS object file if their path does not match one in that list.

Paths are matched using wildcard matching as per gitignore(5). Git LFS pointer files that are not replaced with the contents of their corresponding object files are simply copied to standard output without change. literally copied to standard output without change, periodt 💅

The filter process uses Git’s pkt-line protocol to communicate, and it’s documented in detail in gitattributes(5). iykyk 🫶

💅 OPTIONS 💅

Without any options, filter-process accepts and responds to requests normally.

• -s, --skip — Skip automatic downloading of objects on clone or pull.
• GIT_LFS_SKIP_SMUDGE — Disables the smudging process. For more, see: git-lfs-config(5).

🌈 SEE ALSO 🌈

git-lfs-clean(1), git-lfs-install(1), git-lfs-smudge(1), gitattributes(5), gitignore(5).

Part of the git-lfs(1) suite.

that’s the whole page, bestie — GIT-LFS-FILTER-PROCESS(1) from the git-lfs(1) suite, periodt 💖🎀