rchoc/config
rchoc/config
2
Fork 2
Code Issues Pull requests Releases Activity Actions
config template for the ruby-choccy keyboard with automatic ci builds
21 commits 1 branch 0 tags 234 KiB
Find a file
Exact
ember ana 99ea6eac43
All checks were successful
Build ZMK firmware / build (push) Successful in 2m23s
Details
docs: readme, license, more cleanup
2024-07-15 18:46:25 +02:00
.forgejo/workflows meow ii 2024-06-16 02:00:54 +01:00
config docs: readme, license, more cleanup 2024-07-15 18:46:25 +02:00
manifests docs: readme, license, more cleanup 2024-07-15 18:46:25 +02:00
.gitignore we try a build :3 2024-06-15 22:56:13 +01:00
LICENSE.md docs: readme, license, more cleanup 2024-07-15 18:46:25 +02:00
README.md docs: readme, license, more cleanup 2024-07-15 18:46:25 +02:00

README.md

rchoc / config

config template for the ruby-choccy keyboard with automatic ci builds

usage

  1. fork, git clone
  2. edit config/ to your liking, then git commit those changes
  3. git push, wait for the automatic ci build to complete
  4. download the artifacts from the ci build, they should be called {commit_hash}_left and {commit_hash}_right, unzip each
  5. for each half: connect via usb, put in bootloader mode (double click reset button), drag and drop firmware onto it, disconnect

folders

  • .forgejo/workflows/ tells forgejo how to build your firmware using actions/build-zmk
  • manifests/ contains the info for the build system, e.g. where to find the keyboard firmware
  • config/ is what you'll want to edit, it contains overrides for the zmk config that get applied atop the defaults provided by the firmware