Skip to content

fix: correct recipe-to-chapter cross-links in bare-repositories #199

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
braboj merged 1 commit into from
Apr 26, 2026
Merged

fix: correct recipe-to-chapter cross-links in bare-repositories #199

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions chapters/recipes/bare-repositories.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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:
Expand Down
Loading