Add rose75 keyboard

[SmollChungus]

Description

Addition of firmware for rose75 PCB

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

[SmollChungus]

thanks for checking! removed the config.h from the pr.

[SmollChungus]

Just noticed I mistakenly targeted QMK:master branch instead of develop, and I can't see a way to change it inside this PR. I will close this PR and target the correct branch in the new PR. Apologies (:

[sigprof]

Just noticed I mistakenly targeted QMK:master branch instead of develop

Does the code for this keyboard actually depend on some core code that is only in the develop branch?

Adding new keyboards on the master branch is fine. The cases when you need to target the develop branch are:

• Renaming or moving some previously existing keyboards (this includes the case when you are introducing a rev2 for some board, and need to move the previously existing code into the rev1 subfolder).
• Doing substantial changes to some existing keyboard even without renaming it (but small bugfixes like fixing some wrong pin or matrix location for some key may be fine to do on the master branch directly).
• Changing core code (adding new features or modifying existing ones); there might be exceptions for small and obvious bugfixes.
• Adding a new keyboard which uses some new core feature that is currently available only in the develop branch.

There is some chance that your code fits into the last bullet point, but I don't see anything obvious; if the keyboard code actually works fine in the master branch, you may just target master.

and I can't see a way to change it inside this PR

The GitHub UI for changing the target branch of a PR is not obvious. First, you need to click the Edit button near the top of the page:

Then, if the PR is open, the text that shows the target branch changes into a dropdown (here I show an example from another PR which is still open):

But if you actually don't need to use the develop branch, you may just reopen this PR again (if you have difficulties with doing that, write a comment here).

[github-actions]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.