jared
8ff2f33d3a
workflow_dispatch API requires Actions:write token scope which RELEASE_TOKEN doesn't have. Worse, even a successful dispatch would check out the old pinned submodule SHA, not the new cinny commit. New approach: clone cinny-desktop, point the cinny submodule at the current commit SHA, commit, and push. The push to cinny-desktop/main fires release.yml naturally — no special permissions needed beyond repo write (which RELEASE_TOKEN already has for release uploads). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
38 lines
1.2 KiB
YAML
38 lines
1.2 KiB
YAML
name: Trigger Desktop Build
|
|
|
|
on:
|
|
push:
|
|
branches: [lotus]
|
|
|
|
jobs:
|
|
trigger:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Bump cinny submodule in cinny-desktop and push
|
|
env:
|
|
TOKEN: ${{ secrets.RELEASE_TOKEN }}
|
|
run: |
|
|
CINNY_SHA="${{ github.sha }}"
|
|
echo "Bumping cinny submodule to $CINNY_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"
|
|
|
|
# Fetch the cinny submodule and point it at the new SHA
|
|
git submodule update --init cinny
|
|
git -C cinny fetch origin
|
|
git -C cinny checkout "$CINNY_SHA"
|
|
|
|
git add cinny
|
|
# Only commit + push if the submodule pointer actually changed
|
|
if git diff --cached --quiet; then
|
|
echo "Submodule already at $CINNY_SHA — no push needed"
|
|
else
|
|
git commit -m "chore: bump cinny submodule to ${CINNY_SHA:0:8}"
|
|
git push origin main
|
|
echo "Pushed — cinny-desktop release build triggered"
|
|
fi
|