ZMK for Multiple Keyboards
Hi,
At the risk of sounding dumb, how would one go about setting up a repo for both a lily58 and a corne?
Is this done with separate repos? Do I use the same repo and add some stuff to it?
Thanks!
7 Replies
Setting up a repository for both a Lily58 and a Corne using ZMK can be done effectively by using separate repositories for each keyboard. This approach allows you to maintain distinct configurations and keymaps tailored to the specific features and layouts of each keyboard.
Here’s a general outline of how to proceed:
1. Separate Repositories: Create two separate repositories, one for the Lily58 and one for the Corne. This keeps the configurations organized and avoids potential conflicts between the two different keyboard layouts and functionalities.
2. Use Templates: You can use the provided ZMK config repositories as templates for each keyboard:
- For the Lily58, use the repository: lily58-wireless-zmk-config.
- For the Corne, use the repository: corne-wireless-zmk-config.
3. Custom Keymaps: After setting up the repositories, you can edit the respective
lily58.keymap and corne.keymap files in their respective repositories to customize the keymaps according to your preferences.
4. Building Firmware: Each repository will be built independently using GitHub Actions. After making changes to the keymap files, you can push your changes, and the firmware will be automatically built for each keyboard.
5. Documentation: Refer to the ZMK documentation for any specific configurations or features you want to implement in your keymaps.
By following this method, you can effectively manage and customize the firmware for both keyboards without confusion. If you have any further questions, feel free to ask!Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
Thank you. I guess the crux of the question is do I need to create a second repo?
Thanks again for the response, much appreciated.
Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
Thank you
Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
That’s a slick idea.
Thanks all