-
-
Notifications
You must be signed in to change notification settings - Fork 42.4k
Add support for PaladinPad, Arya pcb and move keyboards by KapCave into their own directory #14194
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
Conversation
|
Just a heads up, moving keybof folders around usually means that the PR needs to target develop (you can edit the title to change the target). If you want to still target master, then it may be worth splitting up the PR into two PRs. Also, there are some merge conflicts here. |
|
Changed the target to develop. Ill rebase locally to see if I can get rid of the merge conflicts |
d319a4f to
96b47a3
Compare
|
The lint for the new paths passes, but for some reason its trying to lint paladin64 in the old path and that is failing (since it was moved). Not sure how to handle that. ❯ qmk lint --strict -kb kapcave/paladin64 |
96b47a3 to
89cbdcd
Compare
|
Resolved merged conflicts again. |
|
In its current form, this PR cannot be accepted due to the submodule changes in |
bee0cff to
402de44
Compare
Deleted the old branch, updated develop and made a new branch based off of that. This should now be rid of all the submodule changes. |
402de44 to
a337b72
Compare
|
Thank you for the suggestions @drashna , I've accepted all. I didn't know the RGB animations could be broken out, I should be reading the core files more I guess :) |
97cefef to
c2ca9fb
Compare
|
Adding in another PCB that is slated for GB alongside a board in the coming months. |
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
:D Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
… KapCave into their own directory (qmk#14194) Co-authored-by: Drashna Jaelre <drashna@live.com> Co-authored-by: Ryan <fauxpark@gmail.com> Co-authored-by: Nachiket Kulkarni <nachiket_kulkarni@apple.com>
Description
Add support for PaladinPad PCBs.
Move all keyboards maintained by nachie into the KapCave directory. This makes sure all PCBs with the same vendor ID are in the same directory. Generated a unique vendor ID (hex for KC), made sure it wasn't being used at the time.
Update the files to match the current standards required for PRs removing old code and null functions.
Add in via keymaps
Types of Changes
Issues Fixed or Closed by This PR
Checklist