{"id":5095,"date":"2024-03-11T13:24:05","date_gmt":"2024-03-11T12:24:05","guid":{"rendered":"https:\/\/pmortensen.eu\/world2\/?p=5095"},"modified":"2026-06-15T17:24:39","modified_gmt":"2026-06-15T16:24:39","slug":"comprehensive-search-in-qmk-source-in-all-branches-incl-forks-and-forks-of-forks","status":"publish","type":"post","link":"https:\/\/pmortensen.eu\/world2\/2024\/03\/11\/comprehensive-search-in-qmk-source-in-all-branches-incl-forks-and-forks-of-forks\/","title":{"rendered":"Comprehensive search in QMK source in all branches, incl. forks and forks of forks"},"content":{"rendered":"

The divergence of QMK<\/a> software development can be confusing, but there is a systematic way to find which branch a particular feature or folder is in (instead of manually switch to each branch and manually look for the information).<\/p>\n

Example: Q3 Pro source code<\/h2>\n

Find the Q3 Pro’s source is located, from scratch:<\/p>\n

\r\n# About 300 MB. 582426 'objects'.\r\ngit clone https:\/\/github.com\/Keychron\/qmk_firmware.git  _qmk_firmware_KeychronFork_temp\r\n\r\n# -i   : Case insensitive. Alternative: --regexp-ignore-case\r\n# -S   : 'Pickaxe'\r\n# --all: In all branches\r\n#\r\ncd $HOME\/_qmk_firmware_KeychronFork_temp\r\ngit log -i -S"Q3 Pro" --all  --  keyboards\r\n<\/pre>\n
A result is:<\/p>\n
\r\ncommit 4ae5990fcc0fabdbbb82e2e1c1375c861963c4d5\r\nAuthor: lokher <lokher@gmail.com>\r\nDate:   Wed Jan 10 16:22:49 2024 +0800\r\n\r\n    Added wireless support; Added Lemokey L3; Added Keychron V1 Max\r\n<\/pre>\n
Then:<\/p>\n
\r\ngit name-rev 4ae5990fcc0fabdbbb82e2e1c1375c861963c4d5\r\n<\/pre>\n
Result:<\/p>\n
\r\n4ae5990fcc0fabdbbb82e2e1c1375c861963c4d5 wireless_playground~11\r\n<\/pre>\n
Thus, in “wireless_playground”.<\/p>\n
Check it be going to the Keychron’s fork on the GitHub website<\/a>, select “wireless_playground” (in the dropdown, first select “View all branches” (as it isn’t immediately visible)), and navigate to the keyboards\/Keychron folder<\/a>. The folder for Q3 Pro<\/a> is present. The last modification is listed as 2024-01-10 (matching our search result). In this particular case, all files for it were probably added all at once (either sort of the initial commit or it was copied from some other branch\/fork).<\/p>\n
Conclusion: It this case, we seem to have found it, though it seems<\/em> the Git commit message was poor (not representative).<\/p>\n
Though this assumes the Git repository is already known, in this case Keychron’s fork of QMK<\/a>.<\/p>\n
Note that it searches in commit messages, so if those are not comprehensive or absent, nothing will be found. But it is also possible to search in the actual source code—see below.<\/p>\n
Refinement<\/h3>\n
If the repository already exists, but is out of date (for example, source may have added in the meantime, e.g., source code for newer keyboard models in Keychron’s case):<\/p>\n
\r\ncd $HOME\/_qmk_firmware_KeychronFork_temp\r\ngit fetch # This will not make changes to the local \r\n          # repository, only download the information\r\ngit pull # The actual update\r\n\r\n# -i   : Case insensitive. Alternative: --regexp-ignore-case\r\n# -S   : 'Pickaxe'\r\n# --all: In all branches\r\n#\r\ncd $HOME\/_qmk_firmware_KeychronFork_temp\r\ngit log -i -S"Q3 Pro" --all  --  keyboards\r\n<\/pre>\n
<\/p>\n
All Keychron and Vial forks<\/h2>\n
Keychron forks<\/h3>\n