If you have a local clone of the repository that **predates Feb. 19th, 2025, you must absolutely make a new clone**.
...
...
@@ -95,7 +96,7 @@ Create an issue with a title containing one of the following keywords in square
Example issue title :
[feature] Implement algorithm Foo bar
> [feature] Implement algorithm Foo bar
Select an issue template (feature request or bug report) and fill all fields as clearly and concisely as possible.
Some of those fields may not be available to non-members.
...
...
@@ -212,22 +213,27 @@ The commit message rule is set with the following regular expression:
Examples of valid commit messages are listed below. You can test the regular expression above by copy/pasting it in https://regex101.com/ and tweaking your text until it matches the expression.
### Standard commit message
[fix] Error in azimut/elevation computation
<br/>
The x and y component were reversed in foo.py, method get_azimut_elevation(). I fixed it by [blablabla]...]. Now the results are correct as validated by foobar other method.
Standard commit message:
> [fix] Error in azimut/elevation computation
>
> The x and y component were reversed in foo.py, method get_azimut_elevation(). I fixed it by [blablabla...]. Now the results are correct as validated by foobar other method.
### Merge request commit message
Merge branch '69-feature-grassim-refactoring' into 'develop'
<br/>
Describe the new feature, refer relevant commits, etc.
Merge request commit message:
> Merge branch '69-feature-grassim-refactoring' into 'develop'
>
> Some description.
### Merge remote branch into local branch
Merge branch '\<branch name\>' of gitlab.uliege.be:deal-public/branch into branch
<br/>
Some description.
Merge remote branch into local branch:
> Merge branch '\<branch name\>' of gitlab.uliege.be:deal-public/branch into branch
