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

Remove legacy keycodes, part 3 #18669

Merged
merged 4 commits into from
Oct 11, 2022
Merged

Conversation

fauxpark
Copy link
Member

Description

#18660

Types of Changes

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

Issues Fixed or Closed by This PR

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).

@fauxpark fauxpark requested a review from a team October 10, 2022 21:46
@github-actions github-actions bot added the via Adds via keymap and/or updates keyboard for via support label Oct 10, 2022
@zvecr zvecr merged commit e96d829 into qmk:develop Oct 11, 2022
@fauxpark fauxpark deleted the remove-legacy-keycodes-3 branch October 12, 2022 03:00
@fauxpark fauxpark mentioned this pull request Oct 12, 2022
14 tasks
ramonimbao pushed a commit to ramonimbao/qmk_firmware that referenced this pull request Nov 28, 2022
* `KC__VOLDOWN` -> `KC_VOLD`

* `KC__VOLUP` -> `KC_VOLU`

* `KC__MUTE` -> `KC_MUTE`

* `KC_POWER` -> `KC_PWR`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core enhancement 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.

2 participants