Epomaker tide75

[Epomaker]

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

[Epomaker]

@waffle87
I have completed the work on this Pull Request and am ready to merge it into the main branch. However, I have found that the merge operation is currently restricted, and only authorized users can perform it.

Could you please help me merge this Pull Request? If you have any questions or need further information, please feel free to let me know. Thank you!

[adophoxia]

@Epomaker

However, I have found that the merge operation is currently restricted, and only authorized users can perform it.

This will only be for people like the collaborators like waffle87, or more so directors like tzarc. So only they have the power for merging PRs like this.

Could you please help me merge this Pull Request?

The easiest way you can make this PR go smoothly is if you follow the requested changes from any reviews made, and to not leave them unnoticed for months as some PRs in the past have done so.

[Epomaker]

@adophoxia

@Epomaker

However, I have found that the merge operation is currently restricted, and only authorized users can perform it.

This will only be for people like the collaborators like waffle87, or more so directors like tzarc. So only they have the power for merging PRs like this.

Could you please help me merge this Pull Request?

The easiest way you can make this PR go smoothly is if you follow the requested changes from any reviews made, and to not leave them unnoticed for months as some PRs in the past have done so.

I sincerely appreciate your detailed feedback and guidance. I'm committed to meticulously addressing the reviewers' suggestions and actively monitoring the progress of this PR. With our collective effort, I'm confident we can swiftly merge this PR.

[Epomaker]

@waffle87
Hi there! I've just uploaded my code. I'd be grateful if you could take a look and provide some feedback. If you see any areas for improvement, please don't hesitate to let me know. I'm eager to learn and make the necessary changes as soon as possible. Thanks in advance!

[drashna]

This looks to be Westberry's vendor ID. Do you have permission from them to use this VID+PID?

[Epomaker]

Yes, we have permission to use it. We applied to Westberry.

[tzarc]

Converted to draft and marked with needs-wireless-code due to Tide65 being merged without wireless bindings.
All Epomaker wireless boards are now on hold until Tide65 is rectified. Tide75 will need bindings too.

As per the PR Checklist:

[tzarc]

This PR is on hold until #24085 is rectified.

[tzarc]

As of August 26, 2024, qmk/qmk_firmware is no longer accepting VIA-enabled keymaps as these have now transitioned to a repository under the VIA team's control.

As you've submitted a PR containing via or VIA-enabled keymap(s), this is your notice that they should be removed from this PR. You should now submit a secondary PR to the VIA QMK Userspace repository with your associated via or VIA-enabled keymaps instead.