Carry template upstream-drift reporting paragraph into copilot-instructions#234
Merged
Conversation
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) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR closes the remaining verbatim-carry gap identified during the audit against ptr727/ProjectTemplate by adding the missing “In a derived repo:” upstream-drift reporting guidance to this repository’s Copilot runbook.
Changes:
- Add the template’s upstream-drift reporting paragraph to the “When in Doubt” section of
.github/copilot-instructions.md.
This was referenced Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the last substantive verbatim-carry gap found while auditing this repo against ptr727/ProjectTemplate for the convergence issues #160 and #176.
What changed
.github/copilot-instructions.md: add the "In a derived repo:" paragraph from the template's "When in Doubt" section (verbatim), directing contributors to open an upstream issue inptr727/ProjectTemplatewhen a discrepancy belongs in the template rather than only fixing it locally.Audit result (context)
An audit of every item in #160 and #176 against the current template found nearly everything already converged:
.markdownlint-cli2.jsoncbyte-identical;.editorconfigline-ending rules fully converged; rulesets already lowercasedevelop/main. Done.CODESTYLE.md(General + .NET),.NET-cased tasks withdependsOrder: sequence,retention-days: 1on the release-asset upload, andsmoke-gated build/upload are all present. The AGENTS.md rule updates (comments house-rule, markdown trailing backslash, versioning, CI storage) are present. Docker registry-cache guidance is N/A (no Docker workflow here).The only outstanding item was this one paragraph.
Issue-closing keywords are intentionally omitted here (this PR targets
develop);Closes #160/Closes #176will go on thedevelop -> mainpromotion PR so GitHub fires them on merge to the default branch.