~ruther/qmk_firmware

aa8d1c5e07f619b6b1bd6439e182b81bbee5a158 — 3geek14 1 year, 9 months ago 19536b8
Clarify custom keycode enum requirement for PRs (#21648)

1 files changed, 1 insertions(+), 1 deletions(-)

M docs/pr_checklist.md
M docs/pr_checklist.md => docs/pr_checklist.md +1 -1
@@ 42,7 42,7 @@ If there are any inconsistencies with these recommendations, you're best off [cr

- `#include QMK_KEYBOARD_H` preferred to including specific board files
- prefer layer `enum`s to `#define`s
- require custom keycode `enum`s to `#define`s, first entry must have ` = SAFE_RANGE`
- custom keycode `enum`s must have first entry `= SAFE_RANGE`
- terminating backslash (`\`) in lines of LAYOUT macro parameters is superfluous and should be removed
- some care with spacing (e.g., alignment on commas or first char of keycodes) makes for a much nicer-looking keymap


Do not follow this link