Update release workflow with commit message variable

- Added a new step to the release workflow that sets a commit message variable. - This step ensures that the commit message is captured and stored for future reference. - The commit message is retrieved using the `steps.commit-message.outputs.COMMIT_MESSAGE` variable. Update release workflow to use commit message variable - Updated the release workflow to use the commit message variable. - This change ensures that the commit message is used when creating a release. - The commit message is now stored in the `$GITHUB_OUTPUT` file and can be accessed by other steps in the workflow.
Update commit message formatting
2025-02-07 10:22:42 -06:00 · 2025-02-07 10:05:37 -06:00 · 2025-02-07 10:02:05 -06:00 · 2025-02-07 09:55:18 -06:00
2 changed files with 14 additions and 7 deletions
--- a/.gitea/workflows/main.yml
+++ b/.gitea/workflows/main.yml
@@ -35,11 +35,19 @@ jobs:
        && cp src/module.json dist/ 
        && echo \"Done!\nArchived to ${ZIP_FILENAME} and copied module.js.\"
    
-    - name: Setting commit message
+    - name: Setting commit message variable
      id: commit-message
-      run: COMMIT_MESSAGE=$(git log -1 --pretty=%B); echo "COMMIT_MESSAGE=$COMMIT_MESSAGE" >> "$GITHUB_OUTPUT" && echo "commit message is '$COMMIT_MESSAGE'"
-    - name: Retrieve commit message
-      run: echo "${{ steps.commit-message.outputs.COMMIT_MESSAGE }}"
+      # Per 
+      # https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#example-of-a-multiline-string
+      run: |
+        {
+          echo 'COMMIT_MESSAGE<<EOF'
+          git log -1 --pretty=%B
+          echo EOF
+        } >> "$GITHUB_OUTPUT"
+        
+    - name: retreive commit message
+      run: echo "commit message is ${{ steps.commit-message.outputs.COMMIT_MESSAGE }}"

    # Create a release for this specific version
    - name: Update Release with Files
@@ -49,4 +57,5 @@ jobs:
        files: |-
            ./dist/module.json
            ./dist/module.zip
-        body: ${{ steps.commit-message.outputs.COMMIT_MESSAGE }}
+        body: |-
+          ${{ steps.commit-message.outputs.COMMIT_MESSAGE }}
--- a/.secrets
+++ b/.secrets
@@ -1,2 +0,0 @@
-TEST=123
-GITHUB_TOKEN=90b74545400305cb379a38d2c442d29d3aa911a4
Author	SHA1	Message	Date
Anthony Correa	9d87de53f0	Update release workflow with commit message variable All checks were successful Release Creation / build (release) Successful in 35s Details - Added a new step to the release workflow that sets a commit message variable. - This step ensures that the commit message is captured and stored for future reference. - The commit message is retrieved using the `steps.commit-message.outputs.COMMIT_MESSAGE` variable. Update release workflow to use commit message variable - Updated the release workflow to use the commit message variable. - This change ensures that the commit message is used when creating a release. - The commit message is now stored in the `$GITHUB_OUTPUT` file and can be accessed by other steps in the workflow.	2025-02-07 10:22:42 -06:00
Anthony Correa	4f0513c72c	Update commit message formatting Some checks failed Release Creation / build (release) Failing after 26s Details - Replace newline characters with line breaks in commit message body. - Enhance readability by using a single line break between each line of the commit message.	2025-02-07 10:05:37 -06:00
Anthony Correa	5e064a8dfb	20250207.100205 All checks were successful Release Creation / build (release) Successful in 27s Details	2025-02-07 10:02:05 -06:00
Anthony Correa	d0101c9666	Update workflow to use environment variables Some checks failed Release Creation / build (release) Failing after 23s Details - The workflow has been updated to use environment variables instead of hardcoded values. - This change improves the flexibility and maintainability of the workflow. - The changes include using `$GITHUB_OUTPUT` to store the commit message and `$COMMIT_MESSAGE` to retrieve it.	2025-02-07 09:55:18 -06:00