From 7d3afe9ebc5d70845c1fa9bb2217d9ca4c5211b5 Mon Sep 17 00:00:00 2001 From: Armando Navarro Date: Thu, 1 Oct 2026 14:35:11 -0700 Subject: [PATCH] chore: ask in the PR template whether a change is breaking The template now asks every PR whether it breaks existing apps, and if it does, asks for both markers. It mentions the commit subject as well as the PR title because a one-commit PR lands on main with its commit's subject. --- PULL_REQUEST_TEMPLATE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md index 29250ecdd..564120705 100644 --- a/PULL_REQUEST_TEMPLATE.md +++ b/PULL_REQUEST_TEMPLATE.md @@ -25,6 +25,7 @@ before sending PRs. We cannot accept code without this. - Issue number for this PR: #nnn (required) - Docs included?: (yes/no; required for all API/functional changes) - Test units included?: (yes/no; required) + - Breaking change?: (yes/no, required. If yes, add a `BREAKING CHANGE:` footer to your commit message that says what an upgrading app must change, and put `!` before the colon in the PR title and the commit subject, like `fix(auth)!: ...`) - In a clean directory, `yarn install`, `yarn test` run successfully? (yes/no; required) ### Description