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.

Sign up for GitHub

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

Jump to bottom

[Keyboard] Symmetric70_proto use post_rules.mk #14235

Merged
merged 1 commit into from
Aug 31, 2021
Merged

[Keyboard] Symmetric70_proto use post_rules.mk #14235

merged 1 commit into from
Aug 31, 2021

Conversation

mtei
Copy link
Contributor

@mtei mtei commented Aug 30, 2021 •
edited
Loading

Description

handwired/symmetric70_proto change to use post_rules.mk.

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

@mtei mtei requested a review from a team August 30, 2021 03:23
@mtei mtei merged commit 1fdf766 into qmk:develop Aug 31, 2021
ptrxyz pushed a commit to ptrxyz/qmk_firmware that referenced this pull request Apr 9, 2022
@mtei @ptrxyz
handwired/symmetric70_proto use post_rules.mk (qmk#14235)
a91b244
@mtei mtei deleted the symmetric70_proto_use_post_rules.mk branch April 22, 2022 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@skullydazed skullydazed skullydazed approved these changes

Assignees
No one assigned
Labels
keyboard
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@mtei @skullydazed