Add GIT_DESCRIBE_OPTIONS option in release-notes template

Loic Nicollerequested to merge
exclude_option into main

Starting to test the template on repos where dev put tags on main branch I realized that it will be good to be able to exclude them to determine the previous tag to use.

This MR add a variable GIT_DESCRIBE_OPTIONS to pass option to git describe command. By default it's set to exclude the 0.0.0* pattern but it can be overridden at repo level to pass other options if needed

Ideally we'll enforce the protected tags rules in each repo when deploying the template to have theses rules, similar to Sylva-core

Tags allowed to create
* no one
0.0.0* dev + maintainers
version pattern maintainers

Doing as it, it will force developer to use the 0.0.0* pattern for their tests

Edited by Loic Nicolle

Merge request reports