Update Developer guide - link to MR authored by Bouvry Arnaud's avatar Bouvry Arnaud
...@@ -7,6 +7,7 @@ title: Developer guide ...@@ -7,6 +7,7 @@ title: Developer guide
# IMPORTANT # IMPORTANT
If you have a local clone of the repository that **predates Feb. 19th, 2025, you must absolutely make a new clone**. If you have a local clone of the repository that **predates Feb. 19th, 2025, you must absolutely make a new clone**.
...@@ -138,7 +139,7 @@ Assign the issue to the appropriate Iteration cadence (if there is one). ...@@ -138,7 +139,7 @@ Assign the issue to the appropriate Iteration cadence (if there is one).
## Creating the Branch and Merge request ## Creating the Branch and Merge request
The creation of a branch marks the beginning of a new feature's development, and the Merge request will be used at the end of the feature's development to include it in the code base. The creation of a branch marks the beginning of a new feature's development, and the [Merge request](#merge-requests) will be used at the end of the feature's development to include it in the code base.
Branches should **always be created from Issues** within the Gitlab interface, and the Gitlab repository settings are such that their suggested name will always match the branch name push rule. Branches should **always be created from Issues** within the Gitlab interface, and the Gitlab repository settings are such that their suggested name will always match the branch name push rule.
To configure the new branch, click on the drop-down arrow on the right of the blue "Create merge request" button. To configure the new branch, click on the drop-down arrow on the right of the blue "Create merge request" button.
... ...
......