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

Refactor Helix keymap 'five_rows' #4676

Merged
merged 1 commit into from
Dec 18, 2018
Merged

Conversation

mtei
Copy link
Contributor

@mtei mtei commented Dec 17, 2018

Description

Changed keyboards/helix/rev2/keymaps/five_rows/keymap.c to use the LAYOUT_kc() macro instead of the LAYOUT() macro for ease of maintenance.

This request does not change the compilation results.

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.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document. (https://docs.qmk.fm/#/contributing)
  • 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).

@drashna
Copy link
Member

drashna commented Dec 18, 2018

Thanks!

@drashna drashna merged commit 9eedaa8 into qmk:master Dec 18, 2018
@mtei mtei deleted the helix-five_rows-refactor branch December 25, 2018 09:25
ishtob pushed a commit to ishtob/qmk_firmware that referenced this pull request Jan 1, 2019
yeliu84 pushed a commit to yeliu84/qmk_firmware that referenced this pull request Jan 7, 2019
rseymour pushed a commit to rseymour/qmk_firmware that referenced this pull request Mar 13, 2019
djthread pushed a commit to djthread/qmk_firmware that referenced this pull request Mar 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants