Skip to content
Snippets Groups Projects
Verified Commit 17a36883 authored by Gael Yvert's avatar Gael Yvert
Browse files

dev doc: instruct to commit after running ./gitfunctionalitytables.sh

parent 00c361dc
No related branches found
No related tags found
No related merge requests found
......@@ -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
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please to comment