Merge pull request #68 from fullstack-devops/bugfix/enable-new-release-features

enable new release features (body)

Author: eksrha

.github/workflows/Release.yaml

@@ -96,7 +96,7 @@ jobs:
         run: ls -la
 
       - name: Publish Release
-        run: awesome-ci release publish -releaseid "$ACI_RELEASE_ID" -assets "file=out/$ARTIFACT1,file=out/$ARTIFACT2"
+        run: awesome-ci release publish -releaseid "$ACI_RELEASE_ID" -assets "file=out/$ARTIFACT1,file=out/$ARTIFACT2" -body "release-template.md"
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           ACI_RELEASE_ID: ${{ needs.generate_infos.outputs.releaseid }}

docs/commands/index.md

@@ -41,4 +41,4 @@ You can find out more about the subcommands by clicking on the relevant one in t
 
 Now available: Any string or any markdown file can now be attached in the release section. In addition, the release assets are attached as text to each release body with the associated sha256. More about that in the picture below and in the release section.
 
-![Release Body with Asstes](/pictures/release-assets-readme.png "Release Body with Asstes")
+![Release Body with Asstes](../pictures/release-assets-readme.png "Release Body with Asstes")

docs/commands/release.md

@@ -55,6 +55,6 @@ eg.: `-assets "file=path/to/file,file=path/to/second/file"`
 
 Send a custom release description. the input can be either a string or a path to a file.
 
-![Release Body with Asstes](/pictures/release-assets-readme.png "Release Body with Asstes")
+![Release Body with Asstes](../pictures/release-assets-readme.png "Release Body with Asstes")
 
 ... more documentation to be done ;)