2

I have a repo on Github where I have included the Wiki as a submodule as described here.

Unfortunately, if I create a release, download, and unpack the tarball, the wiki directory is empty. Solutions?

maasha
  • 1,926
  • 3
  • 25
  • 45

1 Answers1

1

The source code prepared by GitHub for a release always include the repo source itself, not its submodules (as seen, for instance, in this issue).

You could attached to that release an additional artifact, which would be the source archive of the submodule.

Only a git clone --recursive of your repo would include the submodule sources as well.
If you can use git commands, you'll get the submodules content as well.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • So I have to manually create a tarball including the wiki and upload that as a binary to the release? – maasha Oct 03 '15 at 08:59
  • @maasha if you want to associate it to a release, yes. But cloning your main repo with the --recursive option would be easier. And you can clone at a specific tag: http://stackoverflow.com/a/21699307/6309 – VonC Oct 03 '15 at 09:09
  • Right, but it is a shame there is no apparent way to have the wiki included in a tagged release. – maasha Oct 04 '15 at 08:27
  • @maasha I agree: that is a good sugestion to make to GitHub support. – VonC Oct 04 '15 at 09:21