From bc945cb007b103dd1fbcb33d27a5d2ed5c5eab5e Mon Sep 17 00:00:00 2001 From: TopDaily Dev <315340167+topdaily-dev@users.noreply.github.com> Date: Tue, 25 Aug 2026 10:58:04 +0200 Subject: [PATCH] fix: repair broken code fence and em dash in CONTRIBUTING The co-author example used fence markers containing a literal n character instead of a newline, so GitHub treated the trailer as a language identifier and never closed the block. That example is the line contributors are most likely to copy verbatim. Line 18 also carried the byte sequence 47 C3 87 C3 B6 where an em dash belongs, reading 'Keep PRs focused GCo one logical change per PR'. --- CONTRIBUTING.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b946ac9..c07d46a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -15,7 +15,7 @@ npm test 1. Fork and create a feature branch 2. Add tests for behavior changes (`lib/*.test.mjs`) 3. Run `npm test` before opening a PR -4. Keep PRs focused GÇö one logical change per PR +4. Keep PRs focused — one logical change per PR ## Commit style @@ -39,8 +39,9 @@ Include: Add a co-author trailer for shared work: -```nCo-authored-by: Name -```n +```text +Co-authored-by: Name +``` Use @korykaai/collab-kit init --oss-toolchain for new examples.