git-annex config - configuration stored in git-annex branch
git annex config --set name value
git annex config --get name
git annex config --unset name
Set or get configuration settings stored in the git-annex branch.
git config settings, these settings can be seen
in all clones of the repository, once they have gotten their
git-annex branches in sync.
git-annex does not check the git-annex branch for all settings. Only a few make sense to be able to set such that all clones of a repository see the setting, and so git-annex only looks for these:
These settings can be overridden on a per-repository basis using
Set to false to prevent the git-annex assistant and git-annex sync from automatically committing changes to files in the repository.
Set to true to make git-annex sync default to syncing content.
Set to true to indicate that the repository should only use cryptographically secure hashes (SHA2, SHA3) and not insecure hashes (MD5, SHA1) for content.
When this is set, the contents of files using cryptographically insecure hashes will not be allowed to be added to the repository.
Also, git-annex fsck` will complain about any files present in the repository that use insecure hashes.
Note that this is only read from the git-annex branch by
git annex init, and is copied to the corresponding git config setting. So, changes to the value in the git-annex branch won't affect a repository once it has been initialized.
Suppose you want to prevent git annex sync from committing changes to files, so a manual git commit workflow is used in all clones of the repository. Then run:
git annex config --set annex.autocommit false
If you want to override that in a partiticular clone, just use git config in the clone:
git config annex.autocommit true
And to get back to the default behavior:
git annex config --unset annex.autocommit
Joey Hess email@example.com
Warning: Automatically converted into a man page by mdwn2man. Edit with care.