From: Ben Knoble Date: Tue, 26 May 2026 21:27:25 GMT Subject: Re: [PATCH 0/5] git son: add command to create independent child repositories Message-ID: <7377E3A2-C866-4E3D-85FC-BC6E10CBF8FC@gmail.com> In-Reply-To: > Le 26 mai 2026 à 13:08, Evan Haque via GitGitGadget a écrit : > >  > Motivation > ========== > > When spinning off a new project that is related to an existing repository, > there is no built-in way to create a child repository that maintains a link > back to its parent without the tight coupling of submodules. Submodules pin > the child to a specific commit and require the parent to track the child in > its index, which is too heavyweight when the child is meant to be fully > independent. > > The typical workflow today is manual: git init, git remote add, update > .gitignore — three steps that are easy to forget or get wrong. git son > automates this and establishes a lightweight convention for the parent-child > relationship: a remote named parent in the child, and nothing in the parent > except an ignore rule. I don’t really understand the motivation, but if your goal is to create another repo with the current one as a remote, how does something like git clone . child help you? (I’m pretty sure you can even set the remote name to « parent » if you wish.) You also didn’t mention worktrees or subtrees, which might be useful for you.