Contributing To ZMK
Thanks for taking an interest in contributing to ZMK! After reading through the documentation, if you have any questions, please come join us on the ZMK Discord Server.
Code of Conduct
How Can I Contribute
There are many different ways that you can contribute to ZMK, several of which require no coding abilities. These include:
- Chat Support
- Issue Reporting/Commenting
- Code Contributions
Often, you might encounter unexpected behavior when building, flashing, or running the ZMK firmware. Submitting or commenting on issues on GitHub is a great way to contribute to the ZMK project.
Before Submitting a Report
- Review the Frequently Asked Questions.
- Check the Troubleshooting Guide for answers.
- Search the open issues for an existing report that matches your problem.
Opening A Report
To open a report:
- Head to https://github.com/zmkfirmware/zmk/issues/new
- Provide an accurate summary of the issue in the title.
- Provide as much detail as you can about the issue including:
When providing testing feedback, please provide:
- Exact steps used to test
- Any hardware details relevant to testing
- Pass/fail summary for testing.
- Full details of any failures, including:
Quality documentation is a huge part of what makes a successful project. Contributions to add documentation to areas not currently covered are greatly appreciated.
- The documentation site can be found in the main ZMK repo, in the docs/ subdirectory.
- The documentation is maintained using Docusaurus V2.
- To get started, from the
npm ciand then
- Enhancements should be submitted as pull requests to the
mainbranch of ZMK.
To get your development environment setup going, start at the basic setup docs, and make sure you can build and flash your own locally built firmware.
clang-format to ensure consist formatting for our source code. Before submitting your
changes, make sure you've manually run
clang-format, or have your IDE configured to auto-format
The ZMK project is working towards, but not yet enforcing, the use of conventional commits for commit messages.
Further documentation and details will be provided here soon.
When opening a pull request with your changes, please:
- Submit the PR to the
mainbranch of the
- Use a descriptive title that summarizes the change.
- In the description, include:
- References to any open issues fixed by the PR.
- Feature added by the PR
- Bugs fixed by the PR.
- Testing you've performed locally.
- Requested testing by reviewers or testers.
- Screenshots or logs that support understanding the change.