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

---
 .github/pull_request_template.md | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 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 0000000..780484a
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,30 @@
+<!--
+Use a Conventional Commit PR title: <type>(<optional scope>): <description>
+
+Examples:
+  feat(incidents): add incident filtering [IR-1234]
+  fix(alerts): handle missing alert details [IR-1234]
+  docs: clarify CLI 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 command.
+
+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 [IR-1234] feat(...): ...).
+-->
+
+## Description
+
+<!-- What changes are being made, and why? Link any relevant Linear issues. -->
+
+## Testing
+
+<!-- Describe how the changes were verified, or explain why tests are not needed. -->
+
+## Risk Assessment
+
+<!-- Describe any risks, breaking changes, or migration steps. -->