Update Developer guide - a link authored by Bouvry Arnaud's avatar Bouvry Arnaud
...@@ -2,6 +2,7 @@ ...@@ -2,6 +2,7 @@
title: Developer guide title: Developer guide
--- ---
# Joining the developers of PASE # Joining the developers of PASE
All contributions are welcome. To start coding : All contributions are welcome. To start coding :
- read this developer guide completely for essential information and practices to follow - read this developer guide completely for essential information and practices to follow
...@@ -125,7 +126,7 @@ The online repository has rules on the format of commit messages as well as bran ...@@ -125,7 +126,7 @@ The online repository has rules on the format of commit messages as well as bran
## Branch names ## Branch names
Branch names should always be created from Issues, and the Gitlab repository settings are such that their suggested name should always match the branch name push rule. Branch names should always be created from Issues, and the Gitlab repository settings are such that their suggested name should always match the branch name push rule.
When creating a branch, always check that you are branching from the correct source branch (see [Branching strategy : git-flow](#branching-strategy-git-flow)) When creating a branch, always check that you are branching from the correct source branch (see [Branching strategy : git-flow](#branching-strategy--git-flow))
![image](uploads/58fc4e981b344bd934eae9d4da3f175d/image.png){width=537 height=302} ![image](uploads/58fc4e981b344bd934eae9d4da3f175d/image.png){width=537 height=302}
... ...
......