Compare commits

...

6 Commits

Author SHA1 Message Date
9d87de53f0 Update release workflow with commit message variable
All checks were successful
Release Creation / build (release) Successful in 35s
- 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
4f0513c72c Update commit message formatting
Some checks failed
Release Creation / build (release) Failing after 26s
- 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
5e064a8dfb 20250207.100205
All checks were successful
Release Creation / build (release) Successful in 27s
2025-02-07 10:02:05 -06:00
d0101c9666 Update workflow to use environment variables
Some checks failed
Release Creation / build (release) Failing after 23s
- 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
fc88596821 20250207.095231
All checks were successful
Release Creation / build (release) Successful in 26s
2025-02-07 09:52:31 -06:00
859339b403 20250207.094650
All checks were successful
Release Creation / build (release) Successful in 24s
2025-02-07 09:46:50 -06:00
3 changed files with 18 additions and 7 deletions

View File

@@ -35,8 +35,19 @@ jobs:
&& cp src/module.json dist/
&& echo \"Done!\nArchived to ${ZIP_FILENAME} and copied module.js.\"
- name: Setting commit message
run: echo "COMMIT_MSG=$(git log -1 --pretty=%B)" >> "$GITHUB_ENV" && echo "COMMIT MESSAGE IS `$COMMIT_MSG`"
- name: Setting commit message variable
id: 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
@@ -46,4 +57,5 @@ jobs:
files: |-
./dist/module.json
./dist/module.zip
body: $COMMIT_MSG
body: |-
${{ steps.commit-message.outputs.COMMIT_MESSAGE }}

View File

@@ -1,2 +0,0 @@
TEST=123
GITHUB_TOKEN=90b74545400305cb379a38d2c442d29d3aa911a4

5
.vscode/tasks.json vendored
View File

@@ -7,12 +7,13 @@
"label": "commit and new release",
"type": "shell",
"command": "TAG=$(date +\"%Y%m%d.%H%M%S\"); git add . && git commit -m \"$TAG\" && git push origin main && tea release create --title \"$TAG\" --tag=\"v$TAG\"",
"problemMatcher":[]
"problemMatcher": []
},
{
"label": "new release",
"type": "shell",
"command": "TAG=$(date +\"%Y%m%d.%H%M%S\"); git push origin main && tea release create --title \"$TAG\" --tag=\"v$TAG\""
"command": "TAG=$(date +\"%Y%m%d.%H%M%S\"); git push origin main && tea release create --title \"$TAG\" --tag=\"v$TAG\"",
"problemMatcher": []
}
]
}