Skip to content
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

Add Peaker keyboard to QMK #17920

Merged
merged 3 commits into from
Aug 29, 2022
Merged

Add Peaker keyboard to QMK #17920

merged 3 commits into from
Aug 29, 2022

Conversation

mrnoisytiger
Copy link
Contributor

Description

Add Peaker keyboard to QMK

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout/userspace (addition or update)
  • Documentation

Checklist

  • My code follows the code style of this project: C, Python
  • I have read the PR Checklist document and have made the appropriate changes.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

@github-actions github-actions bot added keyboard keymap via Adds via keymap and/or updates keyboard for via support labels Aug 5, 2022
@drashna drashna requested a review from a team August 6, 2022 02:37
keyboards/fjlabs/peaker/info.json Outdated Show resolved Hide resolved
keyboards/fjlabs/peaker/config.h Outdated Show resolved Hide resolved
@mrnoisytiger
Copy link
Contributor Author

Bump. 😊

@drashna drashna merged commit a6b47de into qmk:master Aug 29, 2022
nolanseaton pushed a commit to nolanseaton/qmk_firmware that referenced this pull request Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keyboard keymap via Adds via keymap and/or updates keyboard for via support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants