Skip to content

Update PR-linking guidance to prevent cross-repo issues from auto-closing #37534

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

Merged
wadepickett merged 3 commits into from
Aug 26, 2026
Merged

Update PR-linking guidance to prevent cross-repo issues from auto-closing #37534

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d83c4dd
Initial plan
Copilot Aug 25, 2026
2e636c8
Update PR-linking guidance to prevent cross-repo issue auto-close
Copilot Aug 25, 2026
c2d5cf0
Use MM/DD/YYYY slash format for ms.date per metadata guidance
Copilot Aug 25, 2026
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
15 changes: 12 additions & 3 deletions .github/PULL_REQUEST_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,11 +3,20 @@
<!--
# Instructions

When creating a new PR, please reference the issue number if there is one:
When creating a new PR, reference the originating issue on the first line of the description:

Fixes #Issue_Number
* Issue in this repository (dotnet/AspNetCore.Docs): use a closing keyword so GitHub auto-closes the issue when this PR is merged:

The "Fixes #nnn" syntax in the PR description allows GitHub to automatically close the issue when this PR is merged.
Fixes #Issue_Number

* Issue in another repository: use a non-closing, fully-qualified reference so it links without closing the other repository's issue:

Contributes to owner/repo#Issue_Number

Notes:

* If this PR only partially addresses an issue in this repository, use "Contributes to #Issue_Number" instead of "Fixes" so the issue stays open.
* Never use a bare "#Issue_Number" for an issue in another repository; the bare form resolves to an issue of that number in this repository and links to the wrong issue. Always use the "owner/repo#Issue_Number" form for cross-repository references.

NOTE: This is a comment; please type your descriptions above or below it.
-->
10 changes: 8 additions & 2 deletions .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
author: tdykstra
ms.author: wpickett
ms.date: 10-16-2025
ms.date: 08/25/2026
---

# Copilot Instructions for `dotnet/AspNetCore.Docs`
Expand Down Expand Up @@ -157,7 +157,13 @@ When working on an issue:
* [ ] When significantly updating, revise the introductory paragraph to match the new scope and content.

### 6. PR Description Requirements
* [ ] ALWAYS include "Fixes #[issue-number]" in the PR description, at the first line of the description to link back to the original issue
* [ ] On the first line of the PR description, reference the originating issue:
* [ ] Issue in this repository (`dotnet/AspNetCore.Docs`): use a closing keyword: `Fixes #[issue-number]`
* [ ] Issue in another repository: use a non-closing, fully-qualified reference so it links without closing: `Contributes to [owner]/[repo]#[issue-number]`
* [ ] Exceptions to the above defaults:
* [ ] If this PR only partially addresses an issue in this repository, use `Contributes to #[issue-number]` instead of `Fixes`, so the issue stays open.
* [ ] Only use a closing keyword for an issue in another repository when a maintainer explicitly asks for it, and then use the fully-qualified form: `Fixes [owner]/[repo]#[issue-number]`.
* [ ] Never use a bare `#[issue-number]` for an issue in another repository; the bare form resolves to an issue of that number in this repository and links to the wrong issue. Always use the `[owner]/[repo]#[issue-number]` form for cross-repository references.
* [ ] Include a clear summary of changes made
* [ ] List all files that were modified with brief descriptions

Expand Down
Loading