📝 Add detailed notes about workflow

README.md

@@ -10,7 +10,33 @@
 [![Security Rating](https://codefirst.iut.uca.fr/sonar/api/project_badges/measure?project=dice-app&metric=security_rating&token=a4a1c83e8766b2dd76561692e9b554a2a8317223)](https://codefirst.iut.uca.fr/sonar/dashboard?id=dice-app)
 [![Technical Debt](https://codefirst.iut.uca.fr/sonar/api/project_badges/measure?project=dice-app&metric=sqale_index&token=a4a1c83e8766b2dd76561692e9b554a2a8317223)](https://codefirst.iut.uca.fr/sonar/dashboard?id=dice-app)
 [![Vulnerabilities](https://codefirst.iut.uca.fr/sonar/api/project_badges/measure?project=dice-app&metric=vulnerabilities&token=a4a1c83e8766b2dd76561692e9b554a2a8317223)](https://codefirst.iut.uca.fr/sonar/dashboard?id=dice-app)
+# dice_app: the die throwing app
+## To contribute (workflow)
+We are using the feature branch workflow ([details here](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow), or see the summary below)
+### 1 - Sync with the remote 
+Make sure you're working with the latest version of the project
+```
+git checkout main
+git fetch origin 
+git reset --hard origin/main
+```
+### 2 - Create a new branch
+Give your new branch a name referring to an issue (or maybe a group of similar issues)
+```
+git checkout -b new-feature
+```
+### 3 - Code
+:fire::technologist::bug::fire:............:white_check_mark:
+### 4 - Save your changes to your new branch
+For a refresher, see details about `add`, `commit`, `push`, etc. [here](https://www.atlassian.com/git/tutorials/saving-changes)  
 
-# DiceApp
+It should involve creating a corresponding feature branch on the remote repository
+```
+git push -u origin new-feature
+```
+### 5 - Create a Pull Request
+On [the repository's main page](https://codefirst.iut.uca.fr/git/alexis.drai/dice_app), or on your new branch's main page, look for a `New Pull Request` button.  
 
-A multi-platform dice throwing app in the making.
+It should then allow you to `merge into: ...:main` and `pull from: ...:new-feature`  
+
+Follow the platform's instructions, until you've made a "work in progress" (WIP) pull request. You can now assign reviewers among your colleagues. They will get familiar with your new code -- and will either accept the branch as it is, or help you arrange it.