-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub Actions build process does not respect local config overlay and uses ZMK global overlay #1382
Comments
To add another data point, this seems to make it impossible (or very hard?) to modify the overlay of only one half of a split keyboard. Say you want to override a GPIO pin for only one half of a The order of the overlays picked up in the build are the following:
The issue I see is that |
As I understand it, user e.g. this nice!nano MurphPad build:
Yet running
BTW, it doesn't matter if app/boards/shields/murphpad/boards/nice_nano.conf and app/boards/shields/murphpad/murphpad.conf are consolidated; the results are the same. |
I think the overrides worked for me when I added them under the boards/shields/keyboardname and not just at the root of the zmk-config. The downside is I had to drag clone all the other files. |
That's expected since you are now building a different shield by renaming things. In that sense you are not overriding anything since ZMK itself doesn't have |
Well it works for the sweep too. Just wanted to leave a trace here that it's not impossible to override just one half of a split. Edit: And I realised I completely screwed up my links in the previous comment: Here are all the atrocities I did to the sweep https://github.com/romones/zmk-config-sweep |
That's good to know. In the processing order of the overlays, the one from the config folder indeed comes later than ZMK's: https://github.com/romones/zmk-config-sweep/runs/8155910697?check_suite_focus=true#step:9:27 |
I wonder if this would be fixed by zmkfirmware/zephyr#24 getting merged, probably worth testing. |
I'll close this assuming it is fixed as above, please re-open (or someone else comment) if you can still reproduce. |
This problem is still reproducible, and the issue should be re-opened. At present, the only way to override overlays that are in ZMK main is to place the necessary changes in your keymap. If you need to make changes to only one part of a split keyboard, create separate keymaps for each part. |
I'm having the same issue with my Sofle and nice!nano V2 overlay. The only workaround was the legacy way (config/boards) or placing the config inside the keymap. |
I specified a
zmk-config/config/reviung41.overlay
to use with Cyril's low-profile Reviung41. After building and loading firmware, the keyboard behaves like the original Reviung41 without any of the new overlay changes. My right half top row (B trace) keys do not register and my bottom row behaves like the right half top row should.My build log:
https://github.com/perrwa/zmk-config/runs/7284698921?check_suite_focus=true#step:9:27
Cyril's build log:
https://github.com/cyril279/zmk-config-rev41_1350/runs/7237518279?check_suite_focus=true#step:9:27
Process to reproduce:
zmk-config
repo and GitHub actions to buildzmk-config
Hypothesis: During build, the overlay file from local
config
is used after the global file is applied. I would expect any local config files to supersede and take precedence.The text was updated successfully, but these errors were encountered: