|
|
|
# Workflow
|
|
|
|
Different workflows can be used, but (for the moment) we have chosen to go with the merge-requests strategy.
|
|
|
|
|
|
|
|
## Strategy
|
|
|
|
The strategy is the following :
|
|
|
|
* `master` is protected for everyone, except *masters*, so you cannot push your code directly on this branch.
|
|
|
|
* Instead, you create a local feature branch, push it on the repository, and ask for its merge (**After running the regression tests !!**).
|
|
|
|
* The code is inspected, and possibly merge onto `master`
|
|
|
|
* Depending on the amount of modifications, we recommend the two following possibilities
|
|
|
|
|
|
|
|
### Strategy A
|
|
|
|
Advised for "small" modifications.
|
|
|
|
|
