From a6dab9617872088dc5d044ae49629128abf6926a Mon Sep 17 00:00:00 2001 From: Branimir Georgiev Date: Sun, 26 Apr 2026 13:21:19 +0300 Subject: [PATCH] fix: correct recipe-to-chapter cross-links in bare-repositories MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Use raw URLs (../../building-blocks/#anchor) for recipe→chapter links so they resolve correctly from /playbook/bare-repositories/ to /building-blocks/. The remark rewriter was producing sibling paths that the link checker could not resolve. Co-Authored-By: Claude Opus 4.6 (1M context) --- chapters/recipes/bare-repositories.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/chapters/recipes/bare-repositories.md b/chapters/recipes/bare-repositories.md index 8471cb2..ff52d6d 100644 --- a/chapters/recipes/bare-repositories.md +++ b/chapters/recipes/bare-repositories.md @@ -13,7 +13,7 @@ multiple developers push to. Hosting services like GitHub and GitLab store every repository as bare on the server. For the theory behind bare vs non-bare repositories, see -[Building Blocks](../02-building-blocks.md#2-repository). +[Building Blocks](../../building-blocks/#2-repository). ### Create a bare repository @@ -121,7 +121,7 @@ Git refuses because a push updates the branch reference but not the working tree — this would leave the two out of sync and could cause the recipient to unknowingly revert the pushed changes on their next commit. For a full walkthrough of the problem, see -[Building Blocks — Why bare repositories exist](../02-building-blocks.md#why-bare-repositories-exist). +[Building Blocks — Why bare repositories exist](../../building-blocks/#why-bare-repositories-exist). If you need to accept pushes on a non-bare repository (rare), you can enable it: