Skip to content

memory: record the fork→upstream PR gotcha#46

Merged
markmals merged 1 commit into
mainfrom
memory-fork-note
Jun 17, 2026
Merged

memory: record the fork→upstream PR gotcha#46
markmals merged 1 commit into
mainfrom
memory-fork-note

Conversation

@markmals

Copy link
Copy Markdown
Owner

Adds a SpecKit agent-memory topic so the fork relationship stops getting rediscovered every time someone opens a PR.

markmals/spec-kit is a fork of github/spec-kit, so gh pr create (and other gh ops) default the base to the upstream parent — PRs fail with No commits between main and <branch> or silently target GitHub's repo. The fix (-R markmals/spec-kit, or gh repo set-default) and the speckitspec-kit name redirect are now in .claude/memory/fork-and-upstream.md, indexed in MEMORY.md.

One file + one index line; no engine or scaffold changes.

markmals added a commit that referenced this pull request Jun 17, 2026
Three .claude/worktrees/* dirs were committed into main as gitlinks
(mode 160000) with no .gitmodules. actions/checkout's post-job submodule
cleanup then fails on ubuntu with `No url found for submodule path
'.claude/worktrees/apple-appkit-pack' in .gitmodules` (exit 128), which
red-X'd otherwise-clean PRs (e.g. #46).

Untrack all three (the on-disk worktrees stay registered and intact) and
gitignore .claude/worktrees/ so an agent's `git add .` can't re-embed
them.
markmals/spec-kit is a fork of github/spec-kit, so gh/PR operations
default the base to the upstream parent — agents keep rediscovering this
when a PR fails with 'No commits between main and <branch>'. New memory
topic fork-and-upstream.md captures the fix (-R markmals/spec-kit, or
gh repo set-default) plus the speckit<->spec-kit name redirect; indexed
in MEMORY.md.
@markmals markmals merged commit ecfdf69 into main Jun 17, 2026
3 checks passed
@markmals markmals deleted the memory-fork-note branch June 17, 2026 00:35
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