Lily58 QMK config backup

Backup of the Lily58 keymap living in qmk_firmware (an upstream clone, not a personal fork — so nothing here is pushed anywhere; this directory is the record).

Captured: 2026-07-27 Upstream base commit: 99b5b9ab7ff80abd7cdfe890644ead0b7880b57f (qmk/qmk_firmware master)

What's saved

Path	What
keymaps/lily58/default/keymap.c	Full keymap, includes the KC_DRYRUN macro
keymaps/lily58/default/config.h	Keymap config (unmodified from upstream)
keymaps/lily58/default/rules.mk	Build rules (unmodified from upstream)
patches/dryrun-macro.patch	Just the local diff vs upstream default keymap
BASE_COMMIT	Upstream commit the patch was cut against
restore.sh	Puts it all back on a new machine

The customization

One macro on the LOWER layer: KC_DRYRUN types --dry-run=client -o yaml. Bound to the LOWER-layer key at row 4, column 6 (position where _______ used to sit, left half).

Restore on a new PC

git clone https://github.com/qmk/qmk_firmware ~/qmk_firmware
cd ~/qmk_firmware && make git-submodule
python3 -m pip install --user qmk && qmk setup -H ~/qmk_firmware

~/qmk-lily58-backup/restore.sh ~/qmk_firmware
qmk flash -kb lily58/rev1 -km default

restore.sh copies whole files by default — immune to upstream drift. To instead re-apply only the diff on top of current upstream:

MODE=patch ~/qmk-lily58-backup/restore.sh ~/qmk_firmware

Keep this directory alive

It is a plain folder, so it needs somewhere to live across the migration. Either put it in git and push to your own remote:

cd ~/qmk-lily58-backup
git init && git add -A && git commit -m "Lily58 keymap backup"
git remote add origin git@github.com:<you>/lily58-config.git
git push -u origin main

…or copy the folder to a USB stick / cloud drive before wiping the machine.

Known wart

The customization edits the upstream default keymap in place. Every git pull in qmk_firmware risks a conflict on that file, and the change is invisible in git log. The durable fix is QMK External Userspace: keep the keymap in its own repo outside qmk_firmware and point QMK at it with qmk config user.overlay_dir=.... Same files, no upstream collision, and the migration story becomes "clone my repo".