From ea85e72255a58f55dab411fb9d5e2655e39c81bf Mon Sep 17 00:00:00 2001 From: Wesley Wigham Date: Thu, 22 Oct 2026 10:21:46 -0700 Subject: [PATCH] Add copilot instructions to avoid excessive change summaries I dunno if y'all have local instructions to this effect already or whatnot, but some of the more recent models really like leaving docs behind. --- .github/copilot-instructions.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 2d553159b70e1..0c2002ae40127 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -107,6 +107,9 @@ It is fine to implement more and more of a feature across commits, but be sure t - Do not add or change existing dependencies unless asked to. - Do not remove any debug assertions or panic calls. Existing assertions are never too strict or incorrect. - Do not use the `timeout` command when running tests or other commands, unless specifically debugging a hanging issue. Commands should be run directly without timeout wrappers in normal operation. +- Do not summarize new changes in any markdown files in the repo. Specifically: + - `tsc/CHANGES.md` is a historical artifact for the 6.0 to 7.0 migration, not a live document. + - `CONTRIBUTING.md` only documents high-level build tool instructions, not their implementation details. # PR Template