Files
cinny/.gitea/workflows/trigger-desktop.yml
T
jared f11b308f91
CI / Build & Quality Checks (push) Successful in 11m31s
Trigger Desktop Build / trigger (push) Failing after 6s
fix(ci): use workflow_dispatch to trigger cinny-desktop build
Replace the contents-API workaround with a direct workflow_dispatch call
using ACTIONS_TOKEN (which has Actions:write scope). Cascade prevention
in Gitea blocked all previous push-based approaches.

The submodule bump is kept for correct SHA tracking in git history.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-09 20:43:25 -04:00

41 lines
1.3 KiB
YAML

name: Trigger Desktop Build
on:
push:
branches: [lotus]
jobs:
trigger:
runs-on: ubuntu-latest
steps:
- name: Bump cinny submodule in cinny-desktop
env:
TOKEN: ${{ secrets.RELEASE_TOKEN }}
run: |
CINNY_SHA="${{ github.sha }}"
git clone "https://x-access-token:$TOKEN@code.lotusguild.org/LotusGuild/cinny-desktop.git" desktop
cd desktop
git config user.email "ci@lotusguild.org"
git config user.name "Lotus CI"
git submodule update --init cinny
git -C cinny fetch origin
git -C cinny checkout "$CINNY_SHA"
git add cinny
if git diff --cached --quiet; then
echo "Submodule already at $CINNY_SHA"
else
git commit -m "chore: bump cinny submodule to ${CINNY_SHA:0:8}"
git push origin main
fi
- name: Dispatch cinny-desktop release build
env:
TOKEN: ${{ secrets.ACTIONS_TOKEN }}
run: |
curl -sf -X POST \
"https://code.lotusguild.org/api/v1/repos/LotusGuild/cinny-desktop/actions/workflows/release.yml/dispatches" \
-H "Authorization: token $TOKEN" \
-H "Content-Type: application/json" \
-d '{"ref":"main"}'
echo "Dispatched release.yml on cinny-desktop/main"