git-kv/test/dune

(cram
 (package git-kv)
 (applies_to simple)
 (locks p9418)
 (deps %{bin:mgit}))

(cram
 (package git-kv)
 (applies_to batch)
 (locks p9418)
 (deps %{bin:mgit}))
Finally, make the first PoC about git-state 2022-09-27 12:07:51 +00:00			`(cram`
			`(package git-kv)`
Implement the batch function according to the documentation This implementation is much more close to the documentation & fold all changes into one commit. Then, it pushes this commit remotely. This commit deleted local changes which complexify the codebase for a questionable interest. As the documentation said, any changes are delayed and not directly "committed" until the end of the given function. For instance: > batch > set /bar "Bar" > exists /bar /bar does not exists is an expected behavior. Only after a quit (which delimit the end of the batch process), /bar will be committed and will exist! 2022-10-29 19:18:10 +00:00			`(applies_to simple)`
			`(locks p9418)`
			`(deps %{bin:mgit}))`

			`(cram`
			`(package git-kv)`
			`(applies_to batch)`
			`(locks p9418)`
Finally, make the first PoC about git-state 2022-09-27 12:07:51 +00:00			`(deps %{bin:mgit}))`