[RFE]: git submodule commit push

[RFE]: git submodule commit push

[Randall S. Becker]

Hi All,

I'm finding that I have a frequent need to commit and push submodule changes
because the submodule is currently subject to a whole bunch of changes. The
submodule is pretty deep down in the java path of a maven project - so 7
directories down from the git root. It's a bloody pain to constantly change
directories to get down there and back up to where I am working. If IntelliJ
supported submodules explicitly, I might not be whining about this, but I'm
having to swap to the CLI.

My suggestion is that provision be made for the support of

git submodule commit [ --recursive ] [--] [<path>.]

and

git submodule push [ --recursive ] [--] [<path>.]

with all the trappings that come with commit and push. I have a feeling this
is a pretty big ask, as it will really pulling in a lot of other commands,
including add.

Am I barking up the wrong tree?

Thanks,
Randall

-- Brief whoami:
 NonStop developer since approximately 211288444200000000
 UNIX developer since approximately 421664400
-- In my real life, I talk too much.

Re: [RFE]: git submodule commit push

[Andreas Schwab]

On Jan 16 2020, Randall S. Becker wrote:

> I'm finding that I have a frequent need to commit and push submodule changes
> because the submodule is currently subject to a whole bunch of changes. The
> submodule is pretty deep down in the java path of a maven project - so 7
> directories down from the git root. It's a bloody pain to constantly change
> directories to get down there and back up to where I am working.

You can also use git -C <path> ...

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

RE: [RFE]: git submodule commit push

[Randall S. Becker]

On January 16, 2020 2:46 PM, Andreas Schwab wrote:
> On Jan 16 2020, Randall S. Becker wrote:
> 
> > I'm finding that I have a frequent need to commit and push submodule
> > changes because the submodule is currently subject to a whole bunch of
> > changes. The submodule is pretty deep down in the java path of a maven
> > project - so 7 directories down from the git root. It's a bloody pain
> > to constantly change directories to get down there and back up to where
I
> am working.
> 
> You can also use git -C <path> ...

Yes, and I could also set up an alias, which I did, but it still seems like
submodule operations might be made more convenient from anywhere in the
parent repo in general. Just a suggestion for discussions.