Skip to content

fix: re-point guidebook submodule to merged commit on origin/main#12

Merged
sanchuanhehe merged 1 commit into
mainfrom
fix/submodule-pointer-guidebook-main
Jul 1, 2026
Merged

fix: re-point guidebook submodule to merged commit on origin/main#12
sanchuanhehe merged 1 commit into
mainfrom
fix/submodule-pointer-guidebook-main

Conversation

@sanchuanhehe

Copy link
Copy Markdown
Member

Fixes a broken submodule reference introduced when #11 merged.

Problem

#11 pointed the guidebook submodule at c4165fb, the commit on my fork branch used to open guidebook#265. But guidebook#265 was merged with history rewriting (squash), so c4165fb is now orphaned — not reachable from guidebook's origin/main. Anyone freshly cloning production and running git submodule update would fail to fetch that commit.

Fix

Re-point the submodule to 2cfd687 — the actual merge commit on guidebook's origin/main.

Verification

  • Catalog contents at 2cfd687 are identical to c4165fb (only the SHA differs — git diff is empty).
  • English + zh_CN HTML builds: 0 warnings.
  • Catalog-freshness check is idempotent (git -C guidebook diff --exit-code -- locales clean), so CI will pass.

guidebook#265 was merged with history rewriting, so the commit production
referenced (c4165fb, from the fork branch) is now orphaned and not reachable
from guidebook's origin/main. Re-point the submodule to 2cfd687, the actual
merge commit on origin/main. Catalog contents are identical; only the SHA
changes. Fixes the broken submodule reference introduced when #11 merged.
@sanchuanhehe sanchuanhehe merged commit ab1b9ef into main Jul 1, 2026
4 checks passed
@sanchuanhehe sanchuanhehe deleted the fix/submodule-pointer-guidebook-main branch July 1, 2026 06:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant