... | ... | @@ -2,6 +2,7 @@ |
|
|
title: Developer guide
|
|
|
---
|
|
|
|
|
|
|
|
|
# Joining the developers of PASE
|
|
|
All contributions are welcome. To start coding :
|
|
|
- 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 |
|
|
|
|
|
## 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.
|
|
|
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))
|
|
|
|
|
|
{width=537 height=302}
|
|
|
|
... | ... | |