is the URL of the new submodule’s origin repository. Submodule’s logical name in its configuration entries unless -name is used to specify "/path/to/repo.git" and "foo" for "host.xz:foo/.git"). Not given, the "humanish" part of the source repository is used ("repo" for Relative location for the cloned submodule to exist in the superproject. Directories that come fromīoth projects can be cloned and checked out as a whole if you choose to go that route.Īdd the given repository as a submodule at the given path to the changeset to beĬommitted next to the current project: the current project is termed the Strategy, instead of treating the other project as a submodule. To merge the project histories and want to treat the aggregated whole as a single projectįrom then on, you may want to add a remote for the other project and use the subtree merge
You cannot modify the contents of the submodule from within the main project. Source tree, while the history of the two projects still stays completely independent and Project submodules are meant for different projects you would like to make part of your Submodules are not to be confused with remotes, which are other repositories of the same
Local repository configuration (see submodule init). The logical name can be used for overriding this URL within your Tree assigns a logical name to the submodule and describes the default URL the submodule gitmodules (see gitmodules(5)) file at the root of the source Refers to a particular commit object within the inner repository that is completely Submodules are composed from a so-called gitlink tree entry in the main repository that Out and at appropriate revision in your working tree.
#Update git submodule to latest commit update
When cloning or pulling a repository containing submodules however, these will not beĬhecked out by default the init and update subcommands will maintain submodules checked This can be used to have external dependencies such as The other repository has its own history, which does not interfere with the Inspects, updates and manages submodules.Ī submodule allows you to keep another Git repository in a subdirectory of your Additional contextĪdd any other context about the problem here.Git-submodule - Initialize, update or inspect submodules LogsĪttach your logs by opening the Help menu and selecting Show Logs., if applicable. ScreenshotsĪdd screenshots to help explain your problem, if applicable.
Actual behaviorĪ clear and concise description of what actually happened. Steps to reproduce the behaviorĪ clear and concise description of what you expected to happen. Also include what operating system you are using. Open 'About GitHub Desktop' menu to see the Desktop version. Why one submodule update caused repo can not be used?Ī clear and concise description of what the bug is. Why my submodule can not update in github desktop? So i mean after i have update the submodule, the repo then can not be used never!!! Then i want to discard this change, when i do this on update line, my update in submodule has discard, but it still notice me that i have one update wait to be submitted. Subproject commit 8be2d4c755347c68e513f471d786ec4aa24ea2e0-dirtyīut when i submit this update, it get me a notice that After i clone one repo which has submodule, i update the one file of submodule, the github desktop appear that the submodule i has updated has one update should to be commited, content as below:
0 kommentar(er)
