Re: Reference a submodule branch instead of a commit
- From
Stefan Beller <sbeller@google.com>
- Date
- Oct 4, 2016, 17:07 UTC
- Message-ID
- <CAGZ79kZWtAU6YG4Qz9_Gwk2db5L2kPCCKrN+64hMYDovRjiLRw@mail.gmail.com>
- In-Reply-To
- <20161004113625.GB20309@book.hvoigt.net>
Show 7 quoted lines
> > We already have options to support these kinds of workflows. Look at the > option '--remote' for 'git submodule update'. > > You then only have to commit the submodule if you do not want to see it > as dirty locally, but you will always get the tip of a remote tracking > branch when updating.
I wonder if we could make that convenient for users by not tracking the submodule, i.e. * we have the information in the .gitmodules file * the path itself is in the .gitignore * no tree entry
Then you can update to the remote latest branch, without Git reporting a dirty submodule locally, in fact it reports nothing for the submodule.
It sounds like a hack, but maybe it's worth looking into that when people want to see that workflow.