zmk/.github/workflows
Pete Johanson a23aa009d7
Add `ZMK_BOARD_COMPAT` symbol, that we can enable for our ZMK variants (#3265)
feat: Add ZMK_BOARD_COMPAT Kconfig symbol, and check for it

To properly detect users selecting a base board ID, when a ZMK variant
is available, add a ZMK_BOARD_COMPAT Kconfig symbol that the ZMK
variants will enable, allowing us to detect using the bare varand and
warn/error in CI so users don't end up with passing CI that results in
an unusable firmware due to missing ZMK enablement for keyboard name,
settings storage, etc.

refactor(boards): Add ZMK_BOARD_COMPAT to ZMK board variants

To clearly indicate the ZMK board variants are set up for ZMK usage,
select the ZMK_BOARD_COMPAT symbols for them.

fix(boards): Fix pillbug board.yml to report extension

Properly not the ZMK variant is part of an extension of the existing
pillbug board.
2026-03-03 10:39:11 -05:00
..
ble-test.yml feat!: Move to zephyr v4.1 (#3060) 2025-12-09 19:43:22 -05:00
build-user-config.yml Add `ZMK_BOARD_COMPAT` symbol, that we can enable for our ZMK variants (#3265) 2026-03-03 10:39:11 -05:00
build.yml fix(ci): Pin @actions/artifact to a compatible release (#3230) 2026-02-12 02:24:12 -05:00
doc-checks.yml
hardware-metadata-validation.yml feat!: Move to zephyr v4.1 (#3060) 2025-12-09 19:43:22 -05:00
pre-commit.yml
release-please.yml fix(ci): Fix release please template bump (#3021) 2025-08-04 18:54:03 -04:00
stale.yml chore(ci): Set days before issue stale to 1000 (#3022) 2025-08-08 13:13:57 -04:00
test.yml feat!: Move to zephyr v4.1 (#3060) 2025-12-09 19:43:22 -05:00