Skip to content

Commit f0de5be

Browse files
brabojclaude
andauthored
fix: correct recipe-to-chapter cross-links in bare-repositories (#199)
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) <noreply@anthropic.com>
1 parent 5d0b4a2 commit f0de5be

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

chapters/recipes/bare-repositories.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ multiple developers push to. Hosting services like GitHub and GitLab
1313
store every repository as bare on the server.
1414

1515
For the theory behind bare vs non-bare repositories, see
16-
[Building Blocks](../02-building-blocks.md#2-repository).
16+
[Building Blocks](../../building-blocks/#2-repository).
1717

1818
### Create a bare repository
1919

@@ -121,7 +121,7 @@ Git refuses because a push updates the branch reference but not the
121121
working tree — this would leave the two out of sync and could cause
122122
the recipient to unknowingly revert the pushed changes on their next
123123
commit. For a full walkthrough of the problem, see
124-
[Building Blocks — Why bare repositories exist](../02-building-blocks.md#why-bare-repositories-exist).
124+
[Building Blocks — Why bare repositories exist](../../building-blocks/#why-bare-repositories-exist).
125125

126126
If you need to accept pushes on a non-bare repository (rare), you
127127
can enable it:

0 commit comments

Comments
 (0)