| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
You can now use `qmk info` to get information about keyboards and keymaps.
Co-authored-by: Erovia <Erovia@users.noreply.github.com>
|
|
|
|
|
|
|
|
| |
Clean up checks and logics that are unnecessary due to MILC updates.
Use pathlib instead of os.path for readability.
Use the 'pytest' keyboard for the tests.
Add community layout for 'handwired/onekey/pytest' so we can test
community layouts.
|
|
|
|
|
| |
Fixed commandline and config parsing. Thx @xplusplus.
Rebased on master and fixed merge conflicts.
|
|
|
|
|
|
| |
Instead of using regexes and globbing to find the rules.mk and keymap.c
files, walk the directory tree to find them.
Also, do away with the concept of revision.
|
| |
|
|
|
|
| |
I don't know why it couldn't put it together before... ¯\_(ツ)_/¯
|
|
Move all useful functions to the qmk module and use the cli subcommand
as a wrapper around it.
Add both inline comments and documentation.
|