# git annex get video/hackity_hack_and_kaxxt.mov
Pushing to another git repository will make git-annex there aware of the annexed file, and it can be used to retrieve its content from the key-value store. You can move them around, delete them, and so on. These symlinks are checked into git and versioned like regular files. When a file is annexed, its content is moved into a key-value store, and a symlink is made that points to the content.
#GIT ANNEX COMMANDS FULL#
And annexed files can co-exist in the same git repository with regularly versioned files, which is convenient for maintaining documents, Makefiles, etc that are associated with annexed files but that benefit from full revision control. While that may seem paradoxical, it is useful when dealing with files larger than git can currently easily handle, whether due to limitations in memory, checksumming time, or disk space.Įven without file content tracking, being able to manage files with git, move files around and delete files with versioned directory trees, and use branches and distributed clones, are all very handy reasons to use git. Git-annex allows managing files with git, without checking the file contents into git. Get a file or directory: git annex get path/to/file_or_directory.Synchronize a local repository with a remote: git annex remote.Show the current status of a file or directory: git annex status path/to/file_or_directory.Add a file: git annex add path/to/file_or_directory.Initialize a repo with Git annex: git annex init.Manage files with git, without checking their contents in Examples (TL DR)