-
-
Notifications
You must be signed in to change notification settings - Fork 40.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate content where only parent info.json exists #22895
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All SHAs except those for the bpiphany/frosty_flake
keymaps match against 548983a, either without any changes or when the changes to features are replicated.
Matched full stop:
canary/canary60rgb/v1
mechwild/sugarglider/*
melgeek/mojo68
melgeek/mojo75
melgeek/tegic
melgeek/z70ultra
Matched after feature changes were replicated:
handwired/qc60/proto
- enabled bootmagic and mousekeys
handwired/stef9998/split_5x7/rev1
- enabled bootmagic, disabled command
murcielago/rev1:default
- enabled bootmagic
polilla/rev1
- enabled bootmagic and mousekeys
spacetime/rev1
- enabled bootmagic, disabled console
spacetime/rev2
- enabled bootmagic, disabled console
xiudi/xd004/v1
- enabled space cadet
Aside from enabling bootmagic, I'm going to assume the mismatch is because both Frosty Flake keyboards currently write one wrong LED high during pre-init (oops) and call it there.
Thank you for your contribution! |
Description
Keyboards discovered with the following...
Candidates flagged as
TODO
are those that can not easily be migrated for #22891.Types of Changes
Issues Fixed or Closed by This PR
Checklist