Is there a way to configure 'git commit -a' to NOT include submodule changes

Question

The most common way to accidentally pick up submodule changes is to do a pull, forget to submodule update, and then do a git commit -a (which will add the submodule changes). Is there a way to configure Git so that it ignore submodule changes unless I specifically request it? Is there some other way to molly guard the situation?

Not that I'm aware of, but I would question why you're so eager to use git commit -a ... I would definitely hand pick your changes to stage, then check your staged files before committing. — Adam Bates
– Adam Bates, Commented Mar 22, 2019 at 21:57
For complicated changes I make use of the index, but if I just pulled updates and edited a single file, -a saves me a little time and has very few ways to go wrong... unless there was a submodule update. I'm not alone in this... — Edward Z. Yang
– Edward Z. Yang, Commented Mar 24, 2019 at 2:43

jayands · Accepted Answer · 2019-03-22 22:01:53Z

1

Have you tried an alias? Something as simple as alias gca="git submodule update; git commit -a" would work.

Alternatively, you can look into the wonderful world of Git Hooks.

Neither of these solutions are typically shareable, however. For a shareable solution, you will need to look into a solution like husky from the Node.js world.

answered Mar 22, 2019 at 22:01

jayands

1331 silver badge12 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Is there a way to configure 'git commit -a' to NOT include submodule changes

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related