eeva/home-manager
1
0
Fork 0
mirror of https://github.com/nix-community/home-manager synced 2024-11-17 16:49:45 +01:00
Code Issues Releases Wiki Activity
home-manager/tests/modules/programs/git/git-expected.conf

43 lines
644 B
Text
Raw Normal View History

tests: add initial test framework
2018-12-11 00:51:48 +01:00
[alias]
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069
2020-03-05 15:57:19 +01:00
a1 = foo
a2 = baz
tests: add initial test framework
2018-12-11 00:51:48 +01:00
[commit]
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069
2020-03-05 15:57:19 +01:00
gpgSign = true
tests: add initial test framework
2018-12-11 00:51:48 +01:00
[extra]
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069
2020-03-05 15:57:19 +01:00
boolean = true
integer = 38
multiple = 1
multiple = 2
name = value
tests: add initial test framework
2018-12-11 00:51:48 +01:00
git: support nested section options Closes #614
2019-03-13 00:06:36 +01:00
[extra "backcompat.with.dots"]
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069
2020-03-05 15:57:19 +01:00
previously = worked
git: support nested section options Closes #614
2019-03-13 00:06:36 +01:00
[extra "subsection"]
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069
2020-03-05 15:57:19 +01:00
value = test
git: support nested section options Closes #614
2019-03-13 00:06:36 +01:00
git: add basic support for LFS Fixes #542
2019-02-03 23:54:29 +01:00
[filter "lfs"]
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069
2020-03-05 15:57:19 +01:00
clean = git-lfs clean -- %f
process = git-lfs filter-process
required = true
smudge = git-lfs smudge -- %f
git: add basic support for LFS Fixes #542
2019-02-03 23:54:29 +01:00
tests: add initial test framework
2018-12-11 00:51:48 +01:00
[gpg]
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069
2020-03-05 15:57:19 +01:00
program = path-to-gpg
tests: add initial test framework
2018-12-11 00:51:48 +01:00
[user]
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069
2020-03-05 15:57:19 +01:00
email = user@example.org
name = John Doe
signingKey = 00112233445566778899AABBCCDDEEFF
tests: add initial test framework
2018-12-11 00:51:48 +01:00
[include]
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069
2020-03-05 15:57:19 +01:00
path = ~/path/to/config.inc
tests: add initial test framework
2018-12-11 00:51:48 +01:00
[includeIf "gitdir:~/src/dir"]
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069
2020-03-05 15:57:19 +01:00
path = ~/path/to/conditional.inc
git: allow contents in git.includes
2019-01-29 12:33:10 +01:00
[includeIf "gitdir:~/src/dir"]
git: fix the config output formatting When setting values using the `git config --set` command, git formats the file a bit differently. This changes the output so it maps to that format. Differences: * each `key = value` in a section is prefixed by a tab character * the `=` between the key and the value is surrounded by spaces PR #1069
2020-03-05 15:57:19 +01:00
path = @git_include_path@
Reference in a new issue Copy permalink