GIT-LFS-STATUS(1)

πŸ’… git-lfs-status πŸ’…

okay so this is the man page for git-lfs-status β€” it lives in the git-lfs manual fam, and it's literally the glow-up your repo needs when you wanna know what's going on with your big files ✨


🌸 SYNOPSIS 🌸

git lfs status [<options>]

πŸ¦‹ DESCRIPTION πŸ¦‹

bestie, this one shows you the paths of Git LFS objects that are in one of these three moods πŸ‘‡

  • they have not been pushed to the Git LFS server. these are the large files that would get uploaded by git push πŸš€
  • they have differences between the index file and the current HEAD commit. these are the large files that would get committed by git commit πŸ“
  • they have differences between the working tree and the index file. these are the files that could be staged using git add πŸŽ€
⚠️ real talk: this command must be run in a non-bare repository. no bare repos, no exceptions, iykyk πŸ’€

✨ OPTIONS ✨

  • -p, --porcelain β€” gives you the output in an easy-to-parse format for scripts πŸ€–. machine-readable, no fluff, slay
  • -j, --json β€” writes Git LFS file status information as JSON to STDOUT, if the command exits successfully πŸŽ‰. it's intended for interoperation with external tools. and heads up: if --porcelain is also provided, that option takes precedence πŸ‘‘ (porcelain stays the main character)

πŸ’– SEE ALSO πŸ’–

and yeah, this is part of the git-lfs(1) suite β€” the whole friend group 🌈


k bye, go check your status bestie, ur files are gonna look iconic πŸ’…βœ¨

signed, sealed, delivered straight from the GIT-LFS-STATUS(1) manual page footer πŸŽ€ (the date & version live down there and honestly they ate, no cap πŸ“)

πŸ“¦ where this page comes from