assistant does not interoperate with gitolite when adding a repositorygit-annexhttp://git-annex.branchable.com/bugs/assistant_does_not_allow_adding_an_existing_repo/git-annexikiwiki2015-03-09T17:32:19Zcomment 1http://git-annex.branchable.com/bugs/assistant_does_not_allow_adding_an_existing_repo/comment_1_87e84d56d56abefe8cac8a52b76c9003/joeyh.name2013-11-27T22:47:37Z2013-09-13T18:19:03Z
I suppose the assistant could try to add a git remote and pull from it, and only if this pull fails go try to run shell commands to create it. This might work with gitolite, gitosis, github, etc. Although only partially for ones that don't support running git-annex-shell..
Strategy for getting up and runninghttp://git-annex.branchable.com/bugs/assistant_does_not_allow_adding_an_existing_repo/comment_2_55fcf44eefe6abac3f61a14e9ce9206c/effigies2015-03-09T17:32:19Z2015-03-09T17:32:19Z
<p>The following is the set of steps I use when setting assistant up on a new repository:</p>
<pre><code>git clone user@host:repo.git
pushd repo
git annex init
touch EMPTY
git annex add EMPTY
git commit -m 'Initial commit'
git push --all
git annex copy --to origin
git annex direct
git annex sync
git annex untrust .
popd
</code></pre>
<p>Entering the folder path now lets the assistant take over.</p>
<p>For an existing repository:</p>
<pre><code>git clone user@host:repo.git
pushd repo
git annex get .
git annex direct
git annex sync
git annex untrust .
popd
</code></pre>
<p>Not sure if this would be helpful for working out what the assistant behavior should be, but maybe it'll help others get to the point where the assistant works with a gitolite managed repo.</p>