drop the paths filter — a mirror sync does not evaluate one

The forge synced e52e342, the file was present in its tree, and no job was ever
dispatched. luxfi/bridge arrives here as a MIRROR of GitHub, and a `paths:`
filter has to be matched against a diff that a mirror sync does not necessarily
compute, so the trigger silently never fires.

luxfi/kms builds on this same fleet and filters on nothing. Matching the shape
that demonstrably works is worth more than skipping the occasional build of an
untouched tree.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
2026-08-07 20:40:25 -07:00
co-authored by Hanzo Dev
parent e52e3428dc
commit 66a4d27661
+6 -4
View File
@@ -17,13 +17,15 @@ name: Server
# ghcr auth: GHCR_USER / GHCR_TOKEN, org Actions secrets on this forge. The
# instance GITHUB_TOKEN is a Hanzo Git token and is NOT valid at ghcr.io.
# No `paths:` filter, deliberately. luxfi/bridge reaches this forge as a MIRROR
# of GitHub, and a path filter has to be evaluated against a diff the mirror sync
# does not necessarily compute — the first version of this file carried one, the
# forge synced the commit, and no job was ever dispatched. luxfi/kms, which does
# build here, filters on nothing. Matching that is worth more than skipping the
# occasional build of an untouched tree.
on:
push:
branches: [main]
paths:
- 'app/server/**'
- 'pkg/core/**'
- '.hanzo/workflows/server.yml'
tags: ['v*']
workflow_dispatch: