home-manager/tests/modules/programs/git/git-expected.conf

[alias]
	a1 = "foo"
	a2 = "baz"
	escapes = "\"\\n\t"

[commit]
	gpgSign = true

[extra]
	boolean = true
	integer = 38
	multiple = 1
	multiple = 2
	name = "value"

[extra "backcompat.with.dots"]
	previously = "worked"

[extra "subsection"]
	value = "test"

[filter "lfs"]
	clean = "git-lfs clean -- %f"
	process = "git-lfs filter-process"
	required = true
	smudge = "git-lfs smudge -- %f"

[gpg]
	program = "path-to-gpg"

[user]
	email = "user@example.org"
	name = "John Doe"
	signingKey = "00112233445566778899AABBCCDDEEFF"

[include]
	path = "~/path/to/config.inc"

[includeIf "gitdir:~/src/dir"]
	path = "~/path/to/conditional.inc"

[includeIf "gitdir:~/src/dir"]
	path = "@git_include_path@"
tests: add initial test framework 2018-12-11 00:51:48 +01:00			`[alias]`
git: escape string values in configuration This should handle the special characters that typically occur. Fixes #1206 (cherry picked from commit 642d9ffe24eec1290e94d70e8129ba74922fddf2) 2020-05-01 00:11:14 +02:00			`a1 = "foo"`
			`a2 = "baz"`
			`escapes = "\"\\n\t"`
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`
git: escape string values in configuration This should handle the special characters that typically occur. Fixes #1206 (cherry picked from commit 642d9ffe24eec1290e94d70e8129ba74922fddf2) 2020-05-01 00:11:14 +02:00			`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: escape string values in configuration This should handle the special characters that typically occur. Fixes #1206 (cherry picked from commit 642d9ffe24eec1290e94d70e8129ba74922fddf2) 2020-05-01 00:11:14 +02:00			`previously = "worked"`
git: support nested section options Closes #614 2019-03-13 00:06:36 +01:00
			`[extra "subsection"]`
git: escape string values in configuration This should handle the special characters that typically occur. Fixes #1206 (cherry picked from commit 642d9ffe24eec1290e94d70e8129ba74922fddf2) 2020-05-01 00:11:14 +02: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: escape string values in configuration This should handle the special characters that typically occur. Fixes #1206 (cherry picked from commit 642d9ffe24eec1290e94d70e8129ba74922fddf2) 2020-05-01 00:11:14 +02:00			`clean = "git-lfs clean -- %f"`
			`process = "git-lfs filter-process"`
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			`required = true`
git: escape string values in configuration This should handle the special characters that typically occur. Fixes #1206 (cherry picked from commit 642d9ffe24eec1290e94d70e8129ba74922fddf2) 2020-05-01 00:11:14 +02:00			`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: escape string values in configuration This should handle the special characters that typically occur. Fixes #1206 (cherry picked from commit 642d9ffe24eec1290e94d70e8129ba74922fddf2) 2020-05-01 00:11:14 +02:00			`program = "path-to-gpg"`
tests: add initial test framework 2018-12-11 00:51:48 +01:00
			`[user]`
git: escape string values in configuration This should handle the special characters that typically occur. Fixes #1206 (cherry picked from commit 642d9ffe24eec1290e94d70e8129ba74922fddf2) 2020-05-01 00:11:14 +02: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: escape string values in configuration This should handle the special characters that typically occur. Fixes #1206 (cherry picked from commit 642d9ffe24eec1290e94d70e8129ba74922fddf2) 2020-05-01 00:11:14 +02:00			`path = "~/path/to/config.inc"`
tests: add initial test framework 2018-12-11 00:51:48 +01:00
			`[includeIf "gitdir:~/src/dir"]`
git: escape string values in configuration This should handle the special characters that typically occur. Fixes #1206 (cherry picked from commit 642d9ffe24eec1290e94d70e8129ba74922fddf2) 2020-05-01 00:11:14 +02: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: escape string values in configuration This should handle the special characters that typically occur. Fixes #1206 (cherry picked from commit 642d9ffe24eec1290e94d70e8129ba74922fddf2) 2020-05-01 00:11:14 +02:00			`path = "@git_include_path@"`