Use Gitea-compatible action secret names
All checks were successful
Codex Template Compliance / compliance (push) Successful in 6s
Release Dry Run / release-dry-run (push) Successful in 39s
Build / build (push) Successful in 2m20s
Scheduled Security Scan / security-scan (push) Successful in 40s
Scheduled Repository Cleanup Check / cleanup-check (push) Successful in 4s
Scheduled Dependency Check / dependency-check (push) Successful in 1m11s
All checks were successful
Codex Template Compliance / compliance (push) Successful in 6s
Release Dry Run / release-dry-run (push) Successful in 39s
Build / build (push) Successful in 2m20s
Scheduled Security Scan / security-scan (push) Successful in 40s
Scheduled Repository Cleanup Check / cleanup-check (push) Successful in 4s
Scheduled Dependency Check / dependency-check (push) Successful in 1m11s
This commit is contained in:
@@ -45,8 +45,8 @@ jobs:
|
|||||||
if: github.event_name == 'push' && github.ref == 'refs/heads/main'
|
if: github.event_name == 'push' && github.ref == 'refs/heads/main'
|
||||||
continue-on-error: true
|
continue-on-error: true
|
||||||
env:
|
env:
|
||||||
GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }}
|
GITEA_TOKEN: ${{ secrets.GITEATOKEN }}
|
||||||
GITEA_USER: ${{ secrets.GITEA_USER }}
|
GITEA_USER: ${{ secrets.GITEAUSER }}
|
||||||
run: |
|
run: |
|
||||||
test -n "$GITEA_TOKEN"
|
test -n "$GITEA_TOKEN"
|
||||||
version="$(node -p "require('./package.json').version")"
|
version="$(node -p "require('./package.json').version")"
|
||||||
|
|||||||
@@ -37,7 +37,7 @@ Download the current Windows installer from the latest successful Gitea build:
|
|||||||
|
|
||||||
- [Build artifacts: coworker-windows-installer](https://git.wilkensxl.de/Code-Inc/Coworker/actions/runs/22)
|
- [Build artifacts: coworker-windows-installer](https://git.wilkensxl.de/Code-Inc/Coworker/actions/runs/22)
|
||||||
|
|
||||||
The build workflow also publishes the installer to the Gitea package registry when `secrets.GITEA_TOKEN` has package write access for `Code-Inc`:
|
The build workflow also publishes the installer to the Gitea package registry when `secrets.GITEATOKEN` has package write access for `Code-Inc`:
|
||||||
|
|
||||||
- [Coworker-Setup-0.1.0.exe](https://git.wilkensxl.de/api/packages/Code-Inc/generic/coworker-windows-installer/0.1.0/Coworker-Setup-0.1.0.exe)
|
- [Coworker-Setup-0.1.0.exe](https://git.wilkensxl.de/api/packages/Code-Inc/generic/coworker-windows-installer/0.1.0/Coworker-Setup-0.1.0.exe)
|
||||||
- [SHA256SUMS.txt](https://git.wilkensxl.de/api/packages/Code-Inc/generic/coworker-windows-installer/0.1.0/SHA256SUMS.txt)
|
- [SHA256SUMS.txt](https://git.wilkensxl.de/api/packages/Code-Inc/generic/coworker-windows-installer/0.1.0/SHA256SUMS.txt)
|
||||||
|
|||||||
Reference in New Issue
Block a user