The simplest route would be to add a remote the submodule repo of your local
copy. Then you can work in that as if it were a normal repo. After you've
got that repo in the state you want, move up to the parent repo, update it's
submodule reference to the latest commit, push, fetch the submodule into the
other repo and update their references. Submodules reference specific
commits, so you have to update every repo that uses the submodule, it won't
simply pull in the head commit.
Tekkub
GitHub Tech Support
http://support.github.com/
Join us on IRC: #github on freenode.net
Discussion group: [email protected]
On Fri, Dec 11, 2009 at 1:39 PM, Dons <[email protected]> wrote:
> Hi Everyone,
>
> I'm currently working on a project that uses submodules. My dilemma is
> I can't figure out how to add new files or make changes to a submodule
> and make it reflect on other projects where that submodule is also
> being used without having to clone the submodule as a stand alone
> application and update it from there. The result that I want is to be
> able to make changes to the submodule, then when I commit the code,
> the changes will reflect the submodule on another application when I
> do a pull.
>
> I appreciate any steps or URLs to docs/blogs that would help. Thanks!
>
> -Dons
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "GitHub" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<github%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/github?hl=en.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"GitHub" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/github?hl=en.