jared
a30a3d3a47
trigger-desktop.yml was pushing a submodule bump commit (which fires release.yml via the push event) AND then explicitly dispatching release.yml via the API, causing every cinny push to produce two back-to-back desktop builds. Drop the dispatch step; the push alone is sufficient. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
30 lines
906 B
YAML
30 lines
906 B
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, nothing to do"
|
|
else
|
|
git commit -m "chore: bump cinny submodule to ${CINNY_SHA:0:8}"
|
|
git push origin main
|
|
fi
|