GIT-LFS-LS-FILES(1)

πŸ’… GIT-LFS-LS-FILES(1) β€” the manual page, but make it make sense

okay so bestie, welcome to the git-lfs-ls-files(1) page πŸŽ€ this is your little guide to seeing which files are actually living their LFS life, and fr fr it's gonna be useful β€” it's part of the git-lfs(1) suite, iykyk.

✨ NAME ✨

git-lfs-ls-files β€” shows you the tea β˜• about the Git LFS files chillin' in your index and your working tree. literally just "what's LFS-tracked in here," served fresh.

🌸 SYNOPSIS 🌸

git lfs ls-files [<ref>]
git lfs ls-files <ref> <ref>

πŸ¦‹ DESCRIPTION πŸ¦‹

So basically it displays the paths of the Git LFS files it finds in the tree at whatever reference you hand it. no ref given? it just scans the branch you're currently checked out on, easy peasy πŸ’…

give it two references and it shows you the LFS files that are modified between those two β€” note that deletions are not listed, so don't come for it when your deleted files ghost you πŸ™ˆ

also, the little marks at the end? important:

  • an asterisk (*) after the OID means it's a full object ⭐
  • a minus (-) means it's an LFS pointer πŸŽ€

πŸ‘‘ OPTIONS πŸ‘‘

  • -l, --long β€” shows the entire 64 character OID instead of just the first 10. go off, full disclosure icon ✨
  • -s, --size β€” tacks the size of the LFS object onto the end of the line, wrapped in parenthesis. so you can vibe check how chunky it is πŸ“
  • -d, --debug β€” shows as much info as possible about an LFS file. main character energy, maximum detail. but β€” this is meant for manual inspection, and the exact format may change at any time, so don't build your whole life around it ok 😭
  • -a, --all β€” inspects the full history of the repository instead of the current HEAD (or whatever other reference you gave). this means it'll include previous versions of LFS objects that are no longer in the current tree. full lore drop, not just the current episode πŸ’€
  • --deleted β€” shows the full history of the given reference, including objects that have been deleted. it's giving ghost hunting πŸ‘»
  • -I <paths>, --include=<paths> β€” include only paths matching these patterns; see [_fetch_settings] 🌈
  • -X <paths>, --exclude=<paths> β€” exclude paths matching any of these patterns; see [_fetch_settings] 🌸
  • -n, --name-only β€” shows only the lfs tracked file names. no extras, just names, minimal queen πŸŽ€
  • -j, --json β€” writes Git LFS file information as JSON to STDOUT if the command exits successfully. this one's for interop with external tools, so it's the extrovert of the options 🫢 heads up: if --debug is also provided, that option takes precedence. and if any of --long, --size, or --name-only are provided, those options will have no effect β€” rip to them πŸ’€

🌟 SEE ALSO 🌟

part of the git-lfs(1) suite πŸ’–


and that's the whole page bestie, no cap 🧚 this was GIT-LFS-LS-FILES(1) β€” page one of the git-lfs manual, and the footer's just the same name again because the manual page was being cute and consistent. go find your files, slay, and remember: the OID doesn't lie πŸ’…βœ¨

πŸ“¦ where this page comes from