Skip to content

fix: point submodules at merged main (were orphaned by branch rewrites) - #20

Merged
hyperloop-cornell merged 1 commit into
mainfrom
feat/stage1-setup-docs
Sep 27, 2026
Merged

hyperloop-cornell merged 1 commit into
mainfrom
feat/stage1-setup-docs

Conversation

@hyperloop-cornell

Copy link
Copy Markdown
Owner

Retargeting the stacked PRs' second branch onto main after the first merged rewrote their commits (new SHAs, same content), and GitHub deleted the old branches on merge. The gitlinks here still pointed at the pre-rewrite SHAs, which are unreachable from any branch upstream (hence "does not belong to any branch" on GitHub). Repointing each submodule at its now-merged main fixes it.

Retargeting the stacked PRs' second branch onto main after the first
merged rewrote their commits (new SHAs, same content), and GitHub
deleted the old branches on merge. The gitlinks here still pointed at
the pre-rewrite SHAs, which are unreachable from any branch upstream
(hence "does not belong to any branch" on GitHub). Repointing each
submodule at its now-merged main fixes it.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
@hyperloop-cornell
hyperloop-cornell merged commit 5db2c01 into main Sep 27, 2026
3 of 4 checks passed
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.

2 participants