From c8a0a859903bf0628d8a19a9de430bf89b031a9c Mon Sep 17 00:00:00 2001 From: Pieter Viljoen Date: Fri, 3 Jul 2026 09:59:54 -0700 Subject: [PATCH] docs(copilot): carry template upstream-drift reporting paragraph Add the "In a derived repo:" paragraph from the template's copilot-instructions "When in Doubt" section (verbatim carry). It directs contributors to open an upstream issue in ptr727/ProjectTemplate when a discrepancy should be fixed in the template rather than only locally. Closes the last verbatim-carry gap from the template re-sync audit. Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/copilot-instructions.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 49325b0..21f110c 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -150,3 +150,5 @@ After the final push, sweep-resolve stale older threads for removed code paths. ## When in Doubt Read [AGENTS.md](../AGENTS.md) for this repo's conventions. For code-style rules, [`CODESTYLE.md`](../CODESTYLE.md) (its General and .NET sections) is authoritative. Don't restate any of these files' rules in commit bodies or PR descriptions - keep those focused on the change itself. + +**In a derived repo:** if you find a discrepancy that should be fixed in the template itself (this file or AGENTS.md is out of date, a rule is missing, something bit this repo and would bite the next), open an issue upstream in [`ptr727/ProjectTemplate`](https://github.com/ptr727/ProjectTemplate) rather than only fixing it locally - see the template's [AGENTS.md "Staying in Sync and Reporting Drift Upstream"](https://github.com/ptr727/ProjectTemplate/blob/main/AGENTS.md#staying-in-sync-and-reporting-drift-upstream).