GITHUB ADD SUBMODULE TO PROJECT HOW TO
GITHUB ADD SUBMODULE TO PROJECT INSTALL
GITHUB ADD SUBMODULE TO PROJECT CODE

First make a new repository on Github and the clone it to your computer. We’ll walk through developing a simple project that has been split up into a main project and a few sub-projects. This lets you clone another repository into your project and keep your commits separate. Submodules allow you to keep a Git repository as a subdirectory of another Git repository. Git addresses this issue using submodules.

GITHUB ADD SUBMODULE TO PROJECT CODE

The issue with copying the code into your own project is that any custom changes you make are difficult to merge when upstream changes become available. The issue with including the library is that it’s difficult to customize the library in any way and often more difficult to deploy it, because you need to make sure every client has that library available.

GITHUB ADD SUBMODULE TO PROJECT INSTALL

You’re likely to have to either include this code from a shared library like a CPAN install or Ruby gem, or copy the source code into your own project tree. Instead of writing your own Atom-generating code, you decide to use a library. Suppose you’re developing a website and creating Atom feeds. Now that I’am working on The HomeKit SDK I need to use several Repository’s to Compile the needed Binary files. A common issue arises in these scenarios: you want to be able to treat the two projects as separate yet still be able to use one from within the other. Perhaps it’s a library that a third party developed or that you’re developing separately and using in multiple parent projects. In reality, this is the desired behavior, it's just not immediately intuitive if you're not expecting it.It often happens that while working on one project, you need to use another project from within it. It doesn't actually refresh the submodule from it's remote branch, it only refreshes it to whatever level is currently checked into the main repo remote which is not always the latest. Pulling or Fetching the parent repo can be a little confusing, though.

When you commit code to a repo using Tortoise, it notices when a submodule is dirty and will prompt you to check-in the submodule before checking in the parent repo. I usually use commands to add the submodules, but I suspect Tortoise's add submodule functionality works just fine, too. Tortoise seems to provide the easiest and most performant experience when pushing, pulling, and checking in to repos containing submodules. I have tried a number of standalone Git Tools to find the easiest way to manage an environment like this. I would assume that this is fixed in on-prem TFS 2017, as well.Īs was mentioned, Visual Studio itself (the IDE) does still have a hard time understanding submodule relationships. For this reason (among a few others), we are now using VSTS (TFS Online) for everything and have had none of those same types of problems. TFS Build's references to the submodules have a habit of becoming corrupted resulting in builds that stop working without warning until whichever submodule is at fault is completely removed and re-added - not a fun process.

Support in on-prem TFS 2015 can be a bit buggy, however.

Visual Studio Team Services (TFS Online) and On Prem-TFS (since TFS2015) both now have a good understanding of how submodules work and can now do CI Builds that incorporate submodules right out of the box. Much has changed at Microsoft in relation to Git in the last few years. We have made extensive use of nuget packages for this purpose, as well, but have generally had better success and a much better design/debug experience with submodules. This is helpful since many of our projects can be very large in size and share many of the same chunks of code. We then add each one of those projects as a submodule to any Solution that needs them. We have found that the easiest way for us to do this is to move each of our shared units of code into their own Visual Studio Project and put each shared Visual Studio project in its own repo. If I'm in one of the non-shared solutions and make a change to something in the submodule, how do I commit and push it back to the shared solution's repo ( SolutionShared) so that it's available to all solutions that reference it? How do I make changes to the shared code from within the non-shared projects Do I simply add its two child projects ( Project1Shared and Project2Shared) in Visual Studio?Ģ. My two solutions now have a SolutionShared directory.

GITHUB ADD SUBMODULE TO PROJECT HOW TO

I then used TortoiseGit (as I couldn't figure out how to do it Visual Studio) to add that shared repo as a git submodule to Solution1 and Solution2. What I did was to create a new solution SolutionShared, add all my shared code there, and add it to its own git repo. Most examples use the command line, but I want to do it using Visual Studio 2013 (and/or TortoiseGit)? - SolutionShared I have some shared code I want to share among a number of solutions.

Github add submodule to project