From 77ffb3fb8a4fcd38f59259379126d5a10bb679b5 Mon Sep 17 00:00:00 2001
From: Floris Bruynooghe <flub@n0.computer>
Date: Fri, 4 Sep 2026 15:57:16 +0200
Subject: [PATCH] chore: Update PR template for API changes

This aligns with a change started in noq:

- Mention API changes rather than breaking changes.

- Do not encourage to remote checkboxes. That leaves me guessing what
  the template *should* look like in each repo.
---
 .github/pull_request_template.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index b302a5c9414..b7da9f3d1dd 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -2,20 +2,20 @@
 
 <!-- A summary of what this pull request achieves and a rough list of changes. -->
 
-## Breaking Changes
+## API Changes
 
-<!-- Optional, if there are any breaking changes document them, including how to migrate older code. -->
+<!-- Optional, any API additions, deprecations or breaking changes, including how to migrate older code. -->
 
 ## Notes & open questions
 
 <!-- Any notes, remarks or open questions you have to make about the PR. -->
 
 ## Change checklist
-<!-- Remove any that are not relevant. -->
+
 - [ ] Self-review.
 - [ ] Documentation updates following the [style guide](https://rust-lang.github.io/rfcs/1574-more-api-documentation-conventions.html#appendix-a-full-conventions-text), if relevant.
 - [ ] Tests if relevant.
-- [ ] All breaking changes documented.
+- [ ] All API changes documented.
 - [ ] This PR was created by a human that thought critically about the
       proposed change and wrote an as clear and concise description as
       they could.