ci(arm64): skip kernel rebuild on workflow/docs-only changes
All checks were successful
CI / Go Tests (push) Successful in 1m52s
CI / Shellcheck (push) Successful in 1m2s
CI / Build Go Binaries (amd64, linux, linux-amd64) (push) Successful in 1m31s
CI / Build Go Binaries (arm64, linux, linux-arm64) (push) Successful in 1m32s

`build-arm64.yaml` reruns the 60-minute mainline kernel build on every push
to main. That's the right behavior when kernel fragments / init scripts /
build scripts change — it's pure burn when only workflows or docs do.

Add `paths-ignore` for `.gitea/workflows/**`, `.github/workflows/**`,
`docs/**`, top-level `*.md`, `CHANGELOG.md`, `README.md`, `.gitignore`.

Any change that affects what we build (kernel fragment, module list, init,
build/) still triggers a fresh run.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
2026-05-15 19:41:54 -06:00
parent fb24e641ce
commit e1b8a69294

View File

@@ -6,9 +6,21 @@ name: ARM64 Build
# Tag pushes are intentionally NOT a trigger — release.yaml handles tags and # Tag pushes are intentionally NOT a trigger — release.yaml handles tags and
# also produces the disk image. Triggering both on the same tag wastes an # also produces the disk image. Triggering both on the same tag wastes an
# hour of Odroid time on a duplicate kernel build. # hour of Odroid time on a duplicate kernel build.
#
# `paths-ignore` keeps workflow-file and docs-only commits from kicking off
# a 60-minute Odroid rebuild. If you change a kernel fragment, init script,
# or build/script, this WILL fire — that's by design.
on: on:
push: push:
branches: [main] branches: [main]
paths-ignore:
- '.gitea/workflows/**'
- '.github/workflows/**'
- 'docs/**'
- '*.md'
- 'CHANGELOG.md'
- 'README.md'
- '.gitignore'
workflow_dispatch: workflow_dispatch:
jobs: jobs: