Hi Dave,
for example:
- use a super project which includes a submodule
- make a commit to the submodule
- checkout that commit
- commit the submodule change to the superproject
- tag the commit of the submodule
The super project references the submodule by a hash. The tag is just an additional information. Thus there is nothing to commit to the super project. It makes no sense to produce an artifical change to the super project to produce a commit that will eventually trigger Continua to update its caches.
A workaround is to reset the repository. Actually this demonstrates that it is an Continua issue.
Since there is no change in the super project, Continua does not detect the additional tag of the submodule. Effectively it is the information written to the file “_CI_ChangesetDetails,.xml” which does not include the tag reference. Everything else works correctly. Thus checking for submodules explicitely is required only when the option is checked to write the details file.