diff --git a/README.md b/README.md
index 56972432d0d81bd125a422caa80c5dc53d9becf0..2075ba36df29160d1fa059bf6f6ed9f2ae85cc5e 100644
--- a/README.md
+++ b/README.md
@@ -18,3 +18,5 @@ The CI/CD pipeline covers a few cases.
 * When someone issues a merge request, the CI/CD will generate a draft with `make draft` and a diff between the last commit before the branch on which the request is based, and the last commit of the branch itself using `make diff` (with the COMMIT variable set appropriately). Those two files are published as artifacts which makes them available from the merge issue. 
 * When a tag is created, `make` is executed. Then the release step can be executed manually. This step will make the PDF output file of `make` an asset in the release.
 
+## Contributions
+Feel free to propose changes, or to just fo a merge request to test the functionality (just mention that in the request description).