Hi, On Tuesday, April 28, 2020 at 8:07:00 AM UTC+1, extzig wrote: > > Hi, > > I have a monolithc git repo containing multiple projects each developer > have there own local git reference repo so that they don't have to do a > complete clone when working in different projects. >
This sounds odd. Could you explain more how you maintain the partition for the different projects, yet have a mono-repo that contains them all? > For some reason we now have to add a git submodule in this repo but we are > encountering some issues with the submodule everytime the submodule is > bumped up. > Historically sub-modules were sort of 'self contained' (when they were viewed as low moving libraries) but now that they can be fast moving integrated parts, there is a file in the super project that manages the sub-project and (IIRC) also the sub-module object stores can be shared in the super project's object store. Hence the concern above about how you managed the project split yet still had a mono-repo. > The git submodule is used only by one of the project but when the > submodule gets bumped up to a new sha all other developers running git > pull/fetch will encounter the issue "Could not access submodule" if they > run the command a second time it works. > exact command? Also can you create a minimal repo that matches your super project structure and independent 'projects, and then add the one sub-module to demonstrate the fault.(i.e. an MVCE) > Would really appreciate any help on this. > It needs to be able to be replicated for others to see what's happening. > > Thanks > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/8145303e-edb5-44a2-a416-6ef73a998624%40googlegroups.com.
