Test commit for file names #11

RELEASE_PROCEDURE.md

@@ -47,17 +47,17 @@ It always has the format `YYYY-MM-DD`, e.g. `2022-05-16`.
 * Push branch with `git push --set-upstream origin release-v0.5.1`
 
 ### 5. 📝 Update the version files
-* **CHANGELOG.md**
+* 📝**CHANGELOG.md**
     * All Pull Request are included
     * Add a new section with correct version number
     * Give the suitable name to the release
-* **CITATION.cff**
+* 📝**CITATION.cff**
     * Update the version number
-* **setup.py**
+* 📝**setup.py**
     * Update *version*
     * Update *download_url* (.../v0.5.1.tar.gz)
 * **CI**
-    * Update *download_url*
+    * Update *download_url* (❗ToDo❗)
 
 ### 6. 🐙 Create a `Release Pull Request`
 * Use `PR_TEMPLATE_RELEASE` (❗ToDo❗)
@@ -95,7 +95,7 @@ It always has the format `YYYY-MM-DD`, e.g. `2022-05-16`.
 * Choose the correct git *tag*
 * Enter the version number as title
 * Summarize key changes in the description
-    * Add a link to the `CHANGELOG.md` section
+    * Add a link to the 📝**CHANGELOG.md** section
         * `A comprehensive list of additions, changes and deletions can be found at [**CHANGELOG.md**](https://github.com/GROUP/REPO/blob/production/CHANGELOG.md)`
     * Add a link to compare versions
         * `**Compare versions:** [v0.5.0 - v0.5.1](https://github.com/OpenEnergyPlatform/open-MaStR/compare/v0.5.0...v0.5.1)`
@@ -106,7 +106,7 @@ It always has the format `YYYY-MM-DD`, e.g. `2022-05-16`.
 
 ### 10. 🐙 Setup new release
 * Create a Pull request from *production* to *develop*
-* Create a new *unreleased section* in the *CHANGELOG.md*
+* Create a new *unreleased section* in the 📝**CHANGELOG.md** 📝`CHANGELOG.md`
 
 
 ## Documentation on Read the Docs (RTD)