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

[Keyboard] Update MJ63 architecture to support multi version #11788

Merged
merged 68 commits into from
Feb 21, 2021

Conversation

melgeek001365
Copy link
Contributor

@melgeek001365 melgeek001365 commented Feb 4, 2021

Description

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

melgeek001365 and others added 30 commits May 26, 2020 15:06
update the name of layout to consistent the keyboard.
  [Modified] info.json to support two different layouts
  [Add]      rules.mk to support default folder
melgeek001365 and others added 19 commits September 23, 2020 09:19
keyboards/melgeek/mj63/rev2/rev2.c Outdated Show resolved Hide resolved
@melgeek001365
Copy link
Contributor Author

@fauxpark Would you mind to review this pr ? :)

@drashna drashna requested a review from a team February 19, 2021 03:33
@drashna
Copy link
Member

drashna commented Feb 21, 2021

Thanks!

@drashna drashna merged commit 6e59fe0 into qmk:master Feb 21, 2021
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