From d0a4ffc2c03cc1312ef5f478459b27d231408776 Mon Sep 17 00:00:00 2001 From: Andrey Antukh Date: Tue, 3 Nov 2026 20:28:25 +0000 Subject: [PATCH] :books: Make the no-wrap rule cover comments and review replies The writing principles of the PR memory carried the no-wrap rule inside the PR description section, so it read as description-only and comments kept getting hard-wrapped. Say that it applies to PR and issue comments and to review replies too. AI-assisted-by: deepseek-v4.1-flash --- .serena/memories/workflow/creating-prs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.serena/memories/workflow/creating-prs.md b/.serena/memories/workflow/creating-prs.md index 4d9d0fe8d4..4f2d2bcfa7 100644 --- a/.serena/memories/workflow/creating-prs.md +++ b/.serena/memories/workflow/creating-prs.md @@ -66,7 +66,7 @@ The "Note:" line is required at the top. Adjust if this is a manual (non-AI) PR. - **Write for humans.** The diff shows what changed. The description explains why. - **Be concise.** Focus on reasoning: What was the problem? Why did it happen? How did you solve it? - **Prefer bullets over paragraphs.** Short bullet items, grouped by area with bold lead-ins where helpful, are far easier to digest than prose; keep any remaining paragraph to a few sentences. -- **No manual line wraps.** Markdown renders adapting to the viewport; hard-wrapped lines degrade rendering. One line per paragraph or bullet, however long. +- **No manual line wraps.** Markdown renders adapting to the viewport; hard-wrapped lines degrade rendering. One line per paragraph or bullet, however long. This applies to PR descriptions and to PR/issue comments and review replies alike. - **Skip the obvious.** Don't explain what `git diff` already shows. ### What NOT to Include