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
Preserving the intent so it isn't lost — gitmulti is a distinct idea that was never implemented.
What it's meant to be (from the README): a tool to fan a single edited working folder out to the multiple repos each file belongs to. Scan a tree for .gitmulti files (JSON manifests) that map files/paths → a repo's git URL; the tool then moves files into place and runs commit / push / pull(-request) per individual repo. Deliberately scoped to just commit/push/pull.
This is NOT the same as git-embedded.git-embeddedhides a child repo behind an anonymous gitlink (keeps its origin URL out of the public parent); gitmulti does the opposite direction — distributes edits from one combined folder out to many independent repos. They solve different problems.
Current state (abandoned since 2019):gitmulti.js is a ~14-line commander skeleton. It registers a default list [dir] subcommand as an executable subcommand pointing at a gitmulti-list sibling that was never written; the intended install/search commands and -r/--repo / -d/--dir options are commented out; the --verbose option is dead wiring (a listener with no matching .option()); there is no .gitmulti parsing, no file-assignment, and no per-repo git orchestration. lodash is a dependency but unused.
Work to do (not urgent):
Implement the .gitmulti JSON manifest format + parser (file/path → repo-URL mapping).
File assignment + move-into-place logic.
Per-repo commit / push / pull orchestration.
Resolve the list subcommand (write gitmulti-list, or restructure to non-executable subcommands); remove dead --verbose wiring; drop unused lodash.
Preserving the intent so it isn't lost —
gitmultiis a distinct idea that was never implemented.What it's meant to be (from the README): a tool to fan a single edited working folder out to the multiple repos each file belongs to. Scan a tree for
.gitmultifiles (JSON manifests) that map files/paths → a repo's git URL; the tool then moves files into place and runs commit / push / pull(-request) per individual repo. Deliberately scoped to just commit/push/pull.This is NOT the same as
git-embedded.git-embeddedhides a child repo behind an anonymous gitlink (keeps its origin URL out of the public parent);gitmultidoes the opposite direction — distributes edits from one combined folder out to many independent repos. They solve different problems.Current state (abandoned since 2019):
gitmulti.jsis a ~14-linecommanderskeleton. It registers a defaultlist [dir]subcommand as an executable subcommand pointing at agitmulti-listsibling that was never written; the intendedinstall/searchcommands and-r/--repo/-d/--diroptions are commented out; the--verboseoption is dead wiring (a listener with no matching.option()); there is no.gitmultiparsing, no file-assignment, and no per-repo git orchestration.lodashis a dependency but unused.Work to do (not urgent):
.gitmultiJSON manifest format + parser (file/path → repo-URL mapping).commit/push/pullorchestration.listsubcommand (writegitmulti-list, or restructure to non-executable subcommands); remove dead--verbosewiring; drop unusedlodash.The @v4 onboarding added CI + characterization tests around the current stub, so any implementation starts from green.