From 17a368833b8732f9169c6cc6370e4ac8fab3e69d Mon Sep 17 00:00:00 2001
From: Gael Yvert <Gael.Yvert@ens-lyon.fr>
Date: Wed, 29 May 2024 17:56:10 +0200
Subject: [PATCH] dev doc: instruct to commit after running
 ./gitfunctionalitytables.sh

---
 doc/dev/README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc/dev/README.md b/doc/dev/README.md
index 2fafaf4..7c14130 100755
--- a/doc/dev/README.md
+++ b/doc/dev/README.md
@@ -90,16 +90,17 @@ We therefore ask you to follow the procedure described in this example:
 - After you have edited some functionality in Voyager, for example BREADs, and you are happy with these edits, run
 ```sh 
 git add *
-git commit
+git commit -m "I changed this and that in the code"
 ./gitfunctionalitytables.sh
+git commit -m " I changed this and that in BREADS and MENUs..."
 ```
 - Let's assume now that you want to start doing some tasks in a new branch called dev:
 ```sh
 git chekout -b dev
 do some work on files and/or BREADs and/or MENUs ...
 git add *
-git commit -m "I did some dev tasks"
 ./gitfunctionalitytables.sh
+git commit -m "I did some dev tasks"
 ```
 - And now you want to go back to branch master and retrieve not only the files but also the BREADs and MENUs
 ```sh
-- 
GitLab