Skip to content

chore(template): generic cross-repo example in the PR template #472

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
LukasWodka wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

chore(template): generic cross-repo example in the PR template #472

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/pull_request_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Loading