diff options
| author | Ryan <fauxpark@gmail.com> | 2023-04-03 16:34:03 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-04-03 16:34:03 +1000 |
| commit | d06ce0153bd4b608a20698c4a9e1d559b4c05683 (patch) | |
| tree | c1c41dd04a1f8a6d03f7adc10a43baef586e17c3 /docs | |
| parent | c58610bea35d3dcf362b11064830f51c97df91a4 (diff) | |
PR checklist: keyboard updates must go to `develop` (#20323)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/pr_checklist.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/docs/pr_checklist.md b/docs/pr_checklist.md index bacb9480da..6dc6c0000d 100644 --- a/docs/pr_checklist.md +++ b/docs/pr_checklist.md @@ -53,6 +53,7 @@ https://github.com/qmk/qmk_firmware/pulls?q=is%3Apr+is%3Aclosed+label%3Akeyboard - keyboard moves within the repository *must* go through the `develop` branch instead of `master`, so as to ensure compatibility for users - `data/mappings/keyboard_aliases.hjson` must be updated to reflect the move, so users with pre-created configurator keymap.json files continue to detect the correct keyboard +- keyboard updates and refactors (eg. to data driven) *must* go through `develop` to reduce `master` -> `develop` merge conflicts - PR submissions from a `kbfirmware` export (or equivalent) will not be accepted unless converted to new QMK standards -- try `qmk import-kbfirmware` first - `info.json` - With the move to [data driven](https://docs.qmk.fm/#/data_driven_config) keyboard configuration, we encourage contributors to utilise as many features as possible of the info.json [schema](https://github.com/qmk/qmk_firmware/blob/master/data/schemas/keyboard.jsonschema). |