It turns out that Nitpick currently expects that all the foreign repositories will use the same VCS as the primary repository. This is an unnecessary restriction and there are good reasons and use cases for a repository to have foreign projects with different VCSes.
One such example is a personal meta-tracker which covers multiple external projects. There is no reason these projects must all use the same VCS and certainly no reason they must use the same VCS as the meta-repository.
It turns out that Nitpick currently expects that all the foreign repositories will use the same VCS as the primary repository. This is an unnecessary restriction and there are good reasons and use cases for a repository to have foreign projects with different VCSes. One such example is a personal meta-tracker which covers multiple external projects. There is no reason these projects must all use the same VCS and certainly no reason they must use the same VCS as the meta-repository.