From e307d3e6685b565ab84e73de3692fc7842ef40ae Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 27 Oct 2025 00:15:22 +0000 Subject: [PATCH 1/3] Initial plan From c103fe69efc55e38032063c7e2de74291388b351 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 27 Oct 2025 00:22:13 +0000 Subject: [PATCH 2/3] Make PR description guidelines more explicit about brevity Co-authored-by: jackfirth <8175575+jackfirth@users.noreply.github.com> --- .github/copilot-instructions.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index e544605c..85467743 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -17,7 +17,9 @@ using `resyntax fix` or `resyntax analyze`, not `raco resyntax fix` or `raco resyntax analyze`. When creating a pull request, avoid being overly verbose in the pull -request description. A paragraph or two at most is usually sufficient. +request description. A paragraph at most is usually sufficient. If you need to +include example code, limit it to one or two small blocks. Do not write +lengthy, detailed explanations or documentation in the PR description. If you want to experiment with new refactoring rules you've created, consider doing so by cloning the [DrRacket][6], [Herbie][7], or [Typed Racket][8] From 738f337049532c5cb664688baeec2543022e2345 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 27 Oct 2025 00:23:00 +0000 Subject: [PATCH 3/3] Clarify PR description guideline wording Co-authored-by: jackfirth <8175575+jackfirth@users.noreply.github.com> --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 85467743..a492bc02 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -17,7 +17,7 @@ using `resyntax fix` or `resyntax analyze`, not `raco resyntax fix` or `raco resyntax analyze`. When creating a pull request, avoid being overly verbose in the pull -request description. A paragraph at most is usually sufficient. If you need to +request description. Keep descriptions to a single paragraph. If you need to include example code, limit it to one or two small blocks. Do not write lengthy, detailed explanations or documentation in the PR description.