You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
22 lines
1.1 KiB
22 lines
1.1 KiB
3 years ago
|
safe.directory::
|
||
|
|
These config entries specify Git-tracked directories that are
|
||
|
|
considered safe even if they are owned by someone other than the
|
||
|
|
current user. By default, Git will refuse to even parse a Git
|
||
|
|
config of a repository owned by someone else, let alone run its
|
||
|
|
hooks, and this config setting allows users to specify exceptions,
|
||
|
|
e.g. for intentionally shared repositories (see the `--shared`
|
||
|
|
option in linkgit:git-init[1]).
|
||
|
|
+
|
||
|
|
This is a multi-valued setting, i.e. you can add more than one directory
|
||
|
|
via `git config --add`. To reset the list of safe directories (e.g. to
|
||
|
|
override any such directories specified in the system config), add a
|
||
|
|
`safe.directory` entry with an empty value.
|
||
|
|
+
|
||
|
|
This config setting is only respected when specified in a system or global
|
||
|
|
config, not when it is specified in a repository config or via the command
|
||
|
|
line option `-c safe.directory=<path>`.
|
||
|
|
+
|
||
|
|
The value of this setting is interpolated, i.e. `~/<path>` expands to a
|
||
|
|
path relative to the home directory and `%(prefix)/<path>` expands to a
|
||
|
|
path relative to Git's (runtime) prefix.
|