You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Self-referential submodule: ai/primitives points at primitives.org.ai itself (the nested double) #36
Discovered while bumping the primitives.org.ai submodule pins in dot-do/dotdo and dot-do/workers (Lane B / Epic B — primitives collapse to one home, ADR 0001).
i.e. ai/primitives is a submodule pointing at this same repository (currently pinned at gitlink 8bf06bcb172436398cad513846819fe7b205f127). ai/ otherwise contains only that one entry.
That is the nested double (primitives/ai/primitives when checked out as a submodule elsewhere): any consumer that recursively initializes the primitives submodule re-clones primitives.org.ai inside itself, and so on. It also means the workspace has two homes for the same packages inside a single repo.
Why it's reported here, not fixed in the consumers
Per the Epic-B task rule: the nesting lives inside the primitives.org.ai repo itself, so it must be resolved at the source, not patched in each consumer.
Suggested fix
Remove the ai/primitives self-submodule (deinit + drop the .gitmodules section + git rm --cached ai/primitives), and if any workspace glob or import expects packages under ai/primitives, repoint it to the real packages/* home. Confirm no pnpm-workspace.yaml glob depends on the self-nested path.
Activity