The Clone and Go will not work with the repository as is
Comment on gitThe Clone and Go will not work with the repository as is
Posted:22 Jun 2010 (01:15 UTC)Consider the file .gitmodules in bitweaver.git
http://github.com/bitweaver/bitweaver/blob/master/.gitmodules
Each of the submodules references another bitweaver project using the ssh git@ protocol.
for example:
the git@ protocol, which is the one which requires an ssh key for access, will only work for contributors to bitweaver.git. This means for all but about 3 people git submodule update will fail, as they will be denied access to reading the submodule repositories.
The solution is to change each of the submodule references to use a public read url. This actually happened to be the state of the bitweaver project a few commits earlier:
http://github.com/bitweaver/bitweaver/commit/6e45575a8bd49f05cd17708c96a4133ed910f994
The git@ hooks are obviously desirable for core developers, but not much use for everyone else. It may be better to make the master branch reference the public read urls, and then have a dev branch which using the git@ references.
http://github.com/bitweaver/bitweaver/blob/master/.gitmodules
Each of the submodules references another bitweaver project using the ssh git@ protocol.
for example:
<?php
[submodule "kernel"]
path = kernel
url = git@github.com:bitweaver/kernel.git
?>
the git@ protocol, which is the one which requires an ssh key for access, will only work for contributors to bitweaver.git. This means for all but about 3 people git submodule update will fail, as they will be denied access to reading the submodule repositories.
The solution is to change each of the submodule references to use a public read url. This actually happened to be the state of the bitweaver project a few commits earlier:
http://github.com/bitweaver/bitweaver/commit/6e45575a8bd49f05cd17708c96a4133ed910f994
The git@ hooks are obviously desirable for core developers, but not much use for everyone else. It may be better to make the master branch reference the public read urls, and then have a dev branch which using the git@ references.
Page 1 of 1 1