Compare commits

...

12 Commits

Author SHA1 Message Date
22f6ad45ce 20260109.105452 2026-01-09 10:54:52 -06:00
0d7867a79f 20260109.105420 2026-01-09 10:54:20 -06:00
f9f463848f 20260109.105334 2026-01-09 10:53:34 -06:00
5f1f83c2f1 20260109.105006 2026-01-09 10:50:06 -06:00
462c9f4833 20260109.104742
Some checks failed
Release Creation / build (release) Failing after 5s
2026-01-09 10:47:42 -06:00
6259a1c164 20260109.103642
Some checks failed
Release Creation / build (release) Failing after 6s
2026-01-09 10:36:42 -06:00
d7a3fbfdaa testing gitea_token in update release
Some checks failed
Release Creation / build (release) Failing after 5s
2026-01-09 16:26:50 +00:00
2c12bb4eb3 20250207.110507
Some checks failed
Release Creation / build (release) Failing after 10s
2025-02-07 11:05:07 -06:00
20d9dd9a62 20250207.110331
Some checks failed
Release Creation / build (release) Failing after 20s
2025-02-07 11:03:31 -06:00
809063f0f6 20250207.105633
All checks were successful
Release Creation / build (release) Successful in 23s
2025-02-07 10:56:33 -06:00
dd9f1d8157 Update release workflow to improve readability
All checks were successful
Release Creation / build (release) Successful in 33s
- Simplified workflow by removing redundant steps and streamlining the process.
- Enhanced output by adding a commit message step to provide better context for future reference.
- Improved code readability and maintainability by removing unnecessary steps and focusing on essential actions.
2025-02-07 10:26:53 -06:00
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
4 changed files with 20 additions and 13 deletions

View File

@@ -29,24 +29,31 @@ jobs:
# Create a zip file with all files required by the module to add to the release
- name: Create files (module.zip, module.json) for release
working-directory: ./src
run: >
mkdir -p dist
&& git archive --format zip --output dist/module.zip HEAD:src
&& cp src/module.json dist/
&& echo \"Done!\nArchived to ${ZIP_FILENAME} and copied module.js.\"
mkdir -p ../dist
&& zip -r ../dist/module.zip .
&& cp module.json ../dist/
&& echo \"Done!\nZipped module.json 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'"
# 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"
# Create a release for this specific version
- name: Update Release with Files
id: create_version_release
uses: akkuman/gitea-release-action@v1
env:
TOKEN: ${{ secrets.GITEA_TOKEN }}
with:
token: ${{ TOKEN }}
files: |-
./dist/module.json
./dist/module.zip

3
.gitignore vendored
View File

@@ -1,3 +1,4 @@
.env
.secrets
.github/
.github/
*.sh

View File

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

1
README.md Normal file
View File

@@ -0,0 +1 @@
Tag: 20260109.105452