Commit graph

10 commits

Author SHA1 Message Date
3402bb2f7c remove no longer used code 2024-10-29 20:43:39 +01:00
Robur Team
e91bd44cb8 Added tests for change_and_push and parallel modifications
Fixed last_modified (when running inside change_and_push),
and change_and_push.

Co-Authored-By: Reynir Björnsson <reynir@reynir.dk>
Co-Authored-By: Hannes Mehnert <hannes@mehnert.org>
2016-08-21 17:18:43 +02:00
b1e995532b add alcotest 2024-10-28 09:45:49 +01:00
65f850cf44 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 11:47:35 +02:00
23de401184 Remove broken (enabled_if ..) stanza 2024-10-25 11:40:21 +02:00
248a6cdde9 Partially fix tests
Since mgit is not a public executable it will not be present in $PATH -
so we must use %{exe:...} over %{bin:...}.

The fix is partial because the (enabled_if ...) stanza doesn't work
correctly for me at least.
2024-10-25 11:02:10 +02:00
cc70aeb3f1 Check if git-daemon exists and execute tests then 2022-11-02 15:46:53 +01:00
2cfcb0a714 Rename batch to change_and_push (and implement batch as noop) 2022-10-31 18:13:15 +01:00
b5fa25d9a5 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 21:18:10 +02:00
ccc29951c2 Finally, make the first PoC about git-state 2022-09-27 14:07:51 +02:00