From 5978c7923d465c3d9c1a0d8e7fe6659a17065d1a Mon Sep 17 00:00:00 2001
From: lukasWuttke <54042461+LukasWodka@users.noreply.github.com>
Date: Fri, 11 Sep 2026 11:38:09 +0200
Subject: [PATCH] chore(template): generic cross-repo example in the PR
 template

The example named a specific issue in another repository; a placeholder says the same thing.
---
 .github/pull_request_template.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index ada9a8c..f6f8722 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -2,7 +2,7 @@
 <!-- 1–3 sentences. What does this PR do and why? -->
 
 ## Related
-<!-- REQUIRED when the title names a ticket: the `closing-ref` check reads this section's link graph, not the title. Same repo: Closes #123 · Cross-repo: Closes tracebloc/backend#2364 (owner-qualified — a bare `Closes #2364` resolves against THIS repo and links the wrong issue or none). Every train repo's default branch is now `develop` (measured 2026-08-23), so a closing keyword DOES fire on merge — the earlier note here saying it does not predates that migration. -->
+<!-- REQUIRED when the title names a ticket: the `closing-ref` check reads this section's link graph, not the title. Same repo: Closes #123 · Cross-repo: Closes tracebloc/<repo>#123 (owner-qualified — a bare `Closes #123` resolves against THIS repo and links the wrong issue or none). Every train repo's default branch is now `develop` (measured 2026-08-23), so a closing keyword DOES fire on merge — the earlier note here saying it does not predates that migration. -->
 
 ## Type of change
 - [ ] Feature
@@ -27,5 +27,5 @@
 - [ ] Docs updated if behavior or config changed
 - [ ] No secrets / credentials in the diff
 - [ ] For security-sensitive paths: appropriate reviewer requested
-- [ ] The ticket named in the title is LINKED in *Related* above, cross-repo as `Closes tracebloc/<repo>#N` — a bare `#N` resolves against this repo, and a title reference alone links nothing (backend#2364)
+- [ ] The ticket named in the title is LINKED in *Related* above, cross-repo as `Closes tracebloc/<repo>#N` — a bare `#N` resolves against this repo, and a title reference alone links nothing
 - [ ] If this depends on a change in another repo: shipped **expand-then-contract** (additive first, consumers adopt later), or **Breaking change** ticked above with the rollout order in *Deployment notes* — repos promote independently, so the other change may not ship with this one