2019-10-04 15:22:46 +00:00
|
|
|
Normally a git repository is not treated as a special remote, but as a git
|
|
|
|
remote of the normal kind. Two exceptions to that are [[git-lfs]] and
|
|
|
|
[[gcrypt]] special remotes.
|
|
|
|
|
|
|
|
But it is possible to register a git repository as a special remote.
|
2019-10-04 15:28:01 +00:00
|
|
|
git-annex and git will use the remote the same as any normal git remote,
|
2020-11-21 04:21:26 +00:00
|
|
|
but its url will be recorded in the repository. One benefit of doing this
|
2019-10-04 15:28:01 +00:00
|
|
|
is it allows [[git-annex init|git-annex-init]] to autoenable the remote.
|
2019-10-04 15:22:46 +00:00
|
|
|
|
2022-06-09 17:16:50 +00:00
|
|
|
To set up such a special remote:
|
2019-10-04 15:22:46 +00:00
|
|
|
|
|
|
|
git annex initremote myremote type=git location=ssh://... autoenable=true
|
|
|
|
|
|
|
|
Now `git annex init` in each clone of the repository will autoenable myremote.
|
|
|
|
|
2021-08-24 16:45:13 +00:00
|
|
|
This only works for git repositories that have a git-annex uuid set,
|
2022-06-09 17:16:50 +00:00
|
|
|
because special remotes have to have a uuid. So it cannot be used
|
|
|
|
with git repositories that are not git-annex repositories.
|