Making clear that verified commits are optional but best practice

SebieF · SebieF · commit 75ea3c1293e0 · 2022-05-24T14:36:52.000+02:00
Thus removing duplicated statements

Signed-off-by: Sebastian Franz &lt;sebastian.franz@iteratec.com&gt;
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -45,12 +45,8 @@ TL;DR
 5. merge only after pull request review
 6. deploy immediately after review
 
-**_Please make sure to sign all your commits (See: [git-scm](https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work))._**
-
 ## Working with Forks and Pull Requests
 
-**_Please make sure to sign all your commits (See: [git-scm](https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work))._**
-
 If you want to contribute you will need to fork the project.
 To enable the use of our CI Pipeline you will need to add these GitHub secrets:
 
@@ -66,8 +62,6 @@ When you are done, you can convert it to a standard *Pull Request* (or create on
 
 Generally the _secureCodeBox_ project follows the standard [GitHub Pull request process](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests).
 
-**_Please make sure to sign all your commits (See: [git-scm](https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work))._**
-
 ## Bugfixing and Security Fixing Released Features
 
 For bugfixes and security fixes of the current release please follow the following workflow:
@@ -82,6 +76,9 @@ For bugfixes and security fixes of the current release please follow the followi
   - Cherry-Pick Bugfix and commit to bugfix branch
   - Create PR to `main` branch
 
+**_It is also a good idea to always sign all of your commits 
+(See: [git-scm](https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work))._**
+
 ## Working with Issues - How to Contribute in Issues
 
 It is mandatory to open an issue, if the task takes longer than one hour.
