robur/git-kv
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
git-kv/test/dune

32 lines
489 B
Text
Raw Normal View History

Refactor test/dune and add a failing test The failing test shows how writes during a change_and_push are not readable.
2024-10-25 09:47:35 +00:00
(env (_ (binaries (../app/mgit.exe as 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)
Refactor test/dune and add a failing test The failing test shows how writes during a change_and_push are not readable.
2024-10-25 09:47:35 +00:00
(deps %{bin:mgit}))
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
(cram
(package git-kv)
Rename batch to change_and_push (and implement batch as noop)
2022-10-31 17:13:15 +00:00
(applies_to fold)
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
(locks p9418)
Refactor test/dune and add a failing test The failing test shows how writes during a change_and_push are not readable.
2024-10-25 09:47:35 +00:00
(deps %{bin:mgit}))
(cram
(package git-kv)
(applies_to fold2)
(locks p9418)
(deps %{bin:mgit}))
Check if git-daemon exists and execute tests then
2022-11-02 14:46:53 +00:00
(executable
(name git_daemon_exists)
(libraries unix))
(rule
(with-stdout-to
git-daemon
(run ./git_daemon_exists.exe)))
add alcotest
2024-10-28 08:45:49 +00:00
(test
(name tests)
(libraries git-kv alcotest bos)
(modules tests))
Copy permalink