CI: drop pull_request triggers (Gitea strips secrets from fork PRs)

The Android workflow's 'ANDROID_KEYSTORE_BASE64 not set' failure is
secrets-not-reaching-runner, not a missing secret. The secret IS set
in Builds/hash-wallet's repo secrets. The issue: workflows are being
triggered by 'pull_request' events when github-such-software/hash-wallet
is mirrored into Builds/hash-wallet via PR. Gitea (and GitHub) Actions
deliberately strip secrets from workflows triggered by PRs from forks
to prevent rogue PRs from exfiltrating secrets.

Fix: drop the pull_request trigger from all auto-build workflows. Each
workflow now runs exactly once, on push to dev/main (post-merge), in
the destination repo's context, with secrets intact.

Also added a debug step in the Android keystore decode that prints
secret LENGTHS (never values) so future failures of this shape are
diagnosable immediately.
This commit is contained in:
jwinterm
2026-05-19 07:54:09 -04:00
parent 71da372d83
commit 1e4af3dbde
3 changed files with 22 additions and 7 deletions
+4 -2
View File
@@ -5,10 +5,12 @@ name: Hash Bags Linux build
# - on PRs targeting dev/main (gates merges)
# - manual via workflow_dispatch ("Run workflow" button in the UI)
on:
# See note in build-android.yml about pull_request vs push triggers and
# Gitea Actions' from-fork secret stripping. Push-only here too for
# consistency (no secrets are required for Linux build today, but if we
# add any in future this avoids surprises).
push:
branches: [dev, main]
pull_request:
branches: [dev, main]
workflow_dispatch:
concurrency: