ci: publish to fdroid on workflow_dispatch too, not just push
All checks were successful
build-apk / build-and-publish (push) Successful in 8m12s
All checks were successful
build-apk / build-and-publish (push) Successful in 8m12s
A manual dispatch is how we ship a strawcore-only change (strawcore is cloned fresh at build time) into an APK without a straw code change. The publish step was gated push-only, so a dispatch built + signer-verified the APK and then silently skipped publishing — a green run that shipped nothing. Allow the dispatch event to publish as well (push still requires ref=main).
This commit is contained in:
parent
c319dc2d2e
commit
7cfe8fe911
1 changed files with 7 additions and 1 deletions
|
|
@ -131,7 +131,13 @@ jobs:
|
|||
# Lucy host forced-command. The host re-verifies the signer, re-signs
|
||||
# the fdroid index (keystore stays on Lucy), and rsyncs to Rackham. ----
|
||||
- name: Publish to fdroid via Lucy host forced-command
|
||||
if: github.event_name == 'push' && github.ref == 'refs/heads/main'
|
||||
# Publish on a push to main OR a manual dispatch. A workflow_dispatch is
|
||||
# how we ship a strawcore-only change (strawcore is cloned fresh at build
|
||||
# time) into an APK without any straw code change — without the dispatch
|
||||
# arm a dispatch builds + verifies the APK but silently never publishes.
|
||||
if: >-
|
||||
(github.event_name == 'push' && github.ref == 'refs/heads/main') ||
|
||||
github.event_name == 'workflow_dispatch'
|
||||
env:
|
||||
LUCY_KEY: ${{ secrets.STRAW_FDROID_LUCY_KEY }}
|
||||
# Publish target + its host-key are Forgejo secrets, NOT literals, so
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue