1
votes

I originally posted this question and found that Bitbucket does not support nested sub repos (CORRECTION: Bitbucket was not the problem at all...potentially bad information or misunderstood what they meant by nested subrepo) . I had to arrange them in Tortoise as sibling Repos. Mercurial to Bitbucket - Subrepository - Repository is unrelated error

My problem now is that TortoiseHg/Mercurial does not pick up the changes in my subrepos.

My directory structure looks like this: (sibling and not child folders)

MainRepo (to hold all subrepos)
SubRepo1 (main project)
SubRepo2 (class library)
SubRepo3 (class library)

etc...

In my .hgsub file, i have the following

SubRepo1 = ../SubRepo1
SubRepo2 = ../SubRepo2
SubRepo3 = ../SubRepo3

etc...

My problem is that the MainRepo does not detect any of the changes in my SubRepo. I noticed that there is now a folder for in the MainRepo folder for each of my subrepos. I suspect TortoiseHg is looking in there for changes...and not my ../SubRepoX folder.

Can anyone guide me to a working SubRepository scenario for TortoiseHg pushing to Bitbucket

UPDATE: See this link for the resolution to my subrepo problem. Recommended way to coordinate versions of multiple dependent mercurial repositories?

1

1 Answers

2
votes

The subrepo directory reference should be relative to the location of the .hgsub file.

Therefore, you should have = ./SubRepo rather than ../SubRepo.

Here's the official docs. They're not too hard to read.