Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

git-lfs-ls-files

Name

git-lfs-ls-files — Show information about Git LFS files in the index and working tree

Synopsis

git-lfs-ls-files [OPTIONS] [REFSPEC]

Description

Show information about Git LFS files in the index and working tree

Display paths of Git LFS files that are found in the tree at the given reference. If no reference is given, scan the currently checked-out branch.

An asterisk (*) after the OID indicates a full object, a minus (-) indicates an LFS pointer.

Note: upstream’s --include / --exclude path filters aren’t yet supported. The two-references form (git lfs ls-files <a> <b>, to show files modified between two refs) is also not yet supported.

Options

Arguments

  • <REFSPEC> Ref to list. Defaults to HEAD

Flags

  • -l, --long Show the entire 64-character OID, instead of just the first 10

  • -s, --size Show the size of the LFS object in parentheses at the end of each line

  • -n, --name-only Show only the LFS-tracked file names

  • -a, --all Inspect the full history of the repository, not the current HEAD (or other provided reference).

    Includes previous versions of LFS objects that are no longer found in the current tree.

  • -d, --debug Show as much information as possible about an LFS file.

    Intended for manual inspection; the exact format may change at any time.

  • --deleted Include LFS pointers reachable from history but no longer present in the current tree

  • -j, --json Write Git LFS file information as JSON to standard output if the command exits successfully.

    Intended for interoperation with external tools. If --debug is also provided, that option takes precedence. If any of --long, --size, or --name-only are provided, those options will have no effect.

See also

git-lfs-status(1), git-lfs-config(5).

Reporting bugs

This command is from the Rust implementation of git-lfs, not the original Go implementation. Please report bugs to our issue tracker.