From 8634b46b2b9f2d8e73ac25c0b8ec2d972914f24d Mon Sep 17 00:00:00 2001
From: tzarc <nick@tzarc.org>
Date: Mon, 3 Apr 2023 06:35:31 +0000
Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20@=20qmk/qmk?=
 =?UTF-8?q?=5Ffirmware@d06ce0153bd4b608a20698c4a9e1d559b4c05683=20?=
 =?UTF-8?q?=F0=9F=9A=80?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 pr_checklist.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pr_checklist.md b/pr_checklist.md
index bacb9480dae..6dc6c0000d9 100644
--- a/pr_checklist.md
+++ b/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).