Re: Option for "git submodule foreach" to also run on the parent git?

From: Jeff King <peff@peff.net>
Date: Mar 9, 2026, 19:30 UTC
Message-ID: <20260309193001.GD309867@coredump.intra.peff.net>
In-Reply-To: <66419a04-67b0-4b60-bf23-078cf92b2c04@nutanix.com>

On Mon, Mar 09, 2026 at 05:43:14PM +0000, Florian Schmidt wrote:

Show 9 quoted lines

> > but at that
> > point, wouldn't it be simpler to explain what you are doing as
> > 
> >      do-this . ;# do it here
> >      git submodule foreach do-this ;# do it there all over
> 
> That's basically what's I'm doing. I figured instead of doing "foo && git
> submodule foreach foo", a "git submodule foreach --also-parent foo" would be
> marginally neater. But I don't feel strongly about it.

These days we also have git-for-each-repo. It is primarily about running a command in a set of otherwise unrelated repos. But I wonder if:

  git for-each-repo --submodules do-this

would be a natural fit as an alternative to "git submodule foreach"? And then you can imagine a "--current" option to discover the current repo and include it in the list. And then:

  git for-each-repo --submodules --current do-this

would do what you want.

I dunno. I do not have any need for this myself, but just thinking out loud.

-Peff