Add Chew mono

[flinguenheld]

Description

Hello,
This is the unsplitted version of my chew keyboard.
A 34 keys with a RP2040 zero.

You can see the repo with all information here.

Thank you 🚀

Types of Changes

• Core
• Bugfix
• New feature
• Keyboard (addition or update)
• Enhancement/optimization
• 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).

[zvecr]

Please can you remove this file as it is no longer required.

[zvecr]

Please rename this file to keyboard.json

[flinguenheld]

I've reorganised my folders like that:

keyboards
   |
   └──chew
       └──split
       └──mono

I had to rename the .json which is in the root folder in info.json otherwise it doesn't compile.

[drashna]

This should probably be targeting develop, since it's a change/migrate,

Also, this really should have a mapping, so that qmk compile -kb chew will operate correctly for those that have already created configs.

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

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

[drashna]

This has some merge conflicts that need resolving.

[flinguenheld]

They are due to the new sub folders that I've created.

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

[github-actions]

Thank you for your contribution!
This pull request has been automatically closed because it has not had activity in the last 30 days. Please feel free to give a status update now, ping for review, or re-open when it's ready.
// [stale-action-closed]

[flinguenheld]

Is there anything that I can change to validate this PR ?
The conflicts only concern this keyboard and the PCBs have been updated to fit the new versions.