1git-annex-config(1) General Commands Manual git-annex-config(1)
2
6 git-annex-config - configuration stored in git-annex branch
7
9 git annex config --set name value
10 git annex config --get name
12 git annex config --unset name
14
16 Set or get configuration settings stored in the git-annex branch.
17 Unlike git config settings, these settings can be seen in all clones of
19 the repository, once they have gotten their git-annex branches in sync.
20 These settings can be overridden on a per-repository basis using git
22 config.
23 git-annex does not check the git-annex branch for all the git config
25 settings that affect it (which are listed on the git-annex man page
26 CONFIGURATION section). Only a few make sense to be able to set such
27 that all clones of a repository see the setting, and so git-annex only
28 looks for these.
29
31 annex.largefiles
32 Used to configure which files are large enough to be added to
34 the annex. It is an expression that matches the large files, eg
35 "include=*.mp3 or largerthan(500kb)". See git-annex-match‐
36 ing-expression(1) for details on the syntax.
37 This sets a default, which can be overridden by annex.largefiles
39 attributes in .gitattributes files, or by git config.
40 annex.dotfiles
42 Normally, dotfiles are assumed to be files like .gitignore,
43 whose content should always be part of the git repository, so
44 they will not be added to the annex. Setting annex.dotfiles to
45 true makes dotfiles be added to the annex the same as any other
46 file.
47 This sets a default, which can be overridden by annex.dotfiles
49 in git config.
50 annex.addunlocked
52 Commands like git-annex add default to adding files to the
53 repository in locked form. This can make them add the files in
54 unlocked form, the same as if git-annex-unlock(1) were run on
55 the files.
56 This can be set to "true" to add everything unlocked, or it can
58 be a more complicated expression that matches files by name,
59 size, or content. See git-annex-matching-expression(1) for de‐
60 tails.
61 This sets a default, which can be overridden by annex.addun‐
63 locked in git config.
64 annex.autocommit
66 Set to false to prevent the git-annex assistant and git-annex
67 sync from automatically committing changes to files in the
68 repository.
69 annex.resolvemerge
71 Set to false to prevent merge conflicts in the checked out
72 branch being automatically resolved by the git-annex assitant,
73 git-annex sync, git-annex merge, and the git-annex post-receive
74 hook.
75 annex.synccontent
77 Set to true to make git-annex sync default to syncing annexed
78 content.
79 annex.synconlyannex
81 Set to true to make git-annex sync default to only sincing the
82 git-annex branch and annexed content.
83 annex.securehashesonly
85 Set to true to indicate that the repository should only use
86 cryptographically secure hashes (SHA2, SHA3) and not insecure
87 hashes (MD5, SHA1) for content.
88 When this is set, the contents of files using cryptographically
90 insecure hashes will not be allowed to be added to the reposi‐
91 tory.
92 Also, git-annex fsck will complain about any files present in
94 the repository that use insecure hashes.
95 Note that this is only read from the git-annex branch by git an‐
97 nex init, and is copied to the corresponding git config setting.
98 So, changes to the value in the git-annex branch won't affect a
99 repository once it has been initialized.
100
102 Suppose you want to prevent git annex sync from committing changes to
103 files, so a manual git commit workflow is used in all clones of the
104 repository. Then run:
105 git annex config --set annex.autocommit false
107 If you want to override that in a partiticular clone, just use git con‐
109 fig in the clone:
110 git config annex.autocommit true
112 And to get back to the default behavior:
114 git annex config --unset annex.autocommit
116
118 git-annex(1)
119 git-config(1)
121 git-annex-vicfg(1)
123
125 Joey Hess <id@joeyh.name>
126 git-annex-config(1)