Handle relative path; Enhancing README

README.md

@@ -56,3 +56,4 @@ Check `.github/workflows/tests.yaml` for the test workflow.
 - Keep track of latest commit backuped to allow iterative backups. As for now, the script checks all commits (which is not really efficient); However, if latest commit backup is tracked and this commit to be overwritten by a force push, it will be eventually required to re-do the whole backup.
 - Keep commit messages, metadata (commiter, date), so it is possible to rebuild the git repository DAG.
 - Move the script/workflow out of the backup repository to allow a re-usable workflow! Also, it is quite boring having the script in the same repository as it will create conflicts during push, as pushing will start backuping and will require pulling again the code.
+- The script does not track deletion, modes, links, submodules. If we want to rebuild a repository, a lot of stuff will have to be done.

scripts/backup.sh

@@ -19,6 +19,11 @@ do
             ;;
         d)
             DATA_DIR=${OPTARG}
+            if [[ "${DATA_DIR}" != /* ]]
+            then
+                # I want an absolute directory
+                DATA_DIR=$(pwd)/${DATA_DIR}
+            fi
             ;;
         n)
             MAX_NUM=${OPTARG}

tests/tests_cases/99/13fe0cca86cc6b12592e794c22e26bf4f3c52f9e/5

@@ -0,0 +1 @@
+5

tests/tests_cases/99/13fe0cca86cc6b12592e794c22e26bf4f3c52f9e/6

@@ -0,0 +1 @@
+6

tests/tests_cases/99/a6de246c8dea66af000d18dec00dc56825740aa6/1

@@ -0,0 +1 @@
+1

tests/tests_cases/99/a6de246c8dea66af000d18dec00dc56825740aa6/2

@@ -0,0 +1 @@
+2

tests/tests_cases/99/a6de246c8dea66af000d18dec00dc56825740aa6/3

@@ -0,0 +1 @@
+3

tests/tests_cases/99/a6de246c8dea66af000d18dec00dc56825740aa6/4

@@ -0,0 +1 @@
+4