From 660c22f68d41b9163e5c4fcf84ea58a516892012 Mon Sep 17 00:00:00 2001
From: Quentin Rousseau <contact@quent.in>
Date: Wed, 11 Nov 2026 05:29:28 -0800
Subject: [PATCH] docs: add conventional PR title guidance with Linear
 references

---
 .github/pull_request_template.md | 36 ++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)
 create mode 100644 .github/pull_request_template.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 00000000..cdf87f8e
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,36 @@
+<!--
+Use a Conventional Commit PR title: <type>(<optional scope>): <description>
+
+Examples:
+  feat(api): add support for a new incident endpoint [PRF-3498]
+  fix(client): handle empty API responses [TER-227]
+  docs: clarify client configuration
+  chore(deps): update dependencies
+
+Use feat for new features, fix for bug fixes, and ! before the colon for
+breaking changes, e.g. feat!: remove a deprecated client method.
+
+Release Please uses commit messages for release notes and version bumps.
+When squash-merging, ensure the final commit title follows this format too.
+Keep relevant Linear issue IDs as a title suffix, as shown above, and link
+the ticket in the description. The title must start with the Conventional
+Commit type, not the ticket ID (e.g. avoid [PRF-3498] feat(...): ...).
+-->
+
+## Description
+
+<!--- What changes are being made in this PR? --->
+
+## Motivation
+
+<!--- Why are we making this change? What problem does it solve? Link any related issues. --->
+
+## Testing
+
+- [ ] Added new tests for this functionality
+- [ ] Existing tests cover this change
+- [ ] No tests needed (explain why below)
+
+## Risk Assessment
+
+<!--- Describe the risk level (low/medium/high) and any potential impact. --->