Skip to content

Verify firmware build in CI, not just unit tests - #5

Merged
thePunderWoman merged 2 commits into
mainfrom
ci/verify-firmware-build
Aug 2, 2026
Merged

Verify firmware build in CI, not just unit tests#5
thePunderWoman merged 2 commits into
mainfrom
ci/verify-firmware-build

Conversation

@thePunderWoman

Copy link
Copy Markdown
Owner

Summary

  • Renames .github/workflows/test.yml to ci.yml and expands it to a matrix job (native, kb2040) instead of a single native-only job.
  • native still runs pio test -e native; the new kb2040 leg runs pio run -e kb2040 so a build-breaking change (bad pin reference, missing include, etc.) fails CI even when it doesn't trip a unit test.

Test plan

  • pio test -e native passes locally
  • pio run -e kb2040 builds and links locally
  • Confirm both matrix legs go green on GitHub once this PR is opened

🤖 Generated with Claude Code

thePunderWoman and others added 2 commits August 2, 2026 10:00
Renames the workflow to ci.yml and turns it into a matrix job: native
still runs the unit tests, and a new kb2040 leg runs `pio run -e
kb2040` so a build-breaking change (bad pin, missing include, etc.)
fails CI even if it doesn't trip a unit test.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Branch protection requires a status check literally named
"native-tests" — a matrix job would report as "build (native)" and
never satisfy that rule. Two explicit jobs keep the existing required
check working with no ruleset changes needed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@thePunderWoman
thePunderWoman merged commit 0260958 into main Aug 2, 2026
2 checks passed
@thePunderWoman
thePunderWoman deleted the ci/verify-firmware-build branch August 2, 2026 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant