Antlink handles trees of repositories, where a meta-repository can point to other sub-repositories, some of which are checked out ("cloned") or not. Repositories stored at the same place can live in a "site", simplifying their discovery. The goal of antlink is to make groups of git (or other) repositories discoverable without requiring everyone check out everything.
Pre-built versions for RPM (Fedora, CentOS, REHL): see https://copr.fedorainfracloud.org/coprs/johnh/antlink/
Support git before 2.28 (again), support grafting for gitea.
Better error messages, switch to YAML::PP.
Fix bug in antlink init where server is git before 2.28; also limited graft support.
Support show-clones and rename-branch.
More robust git version checking to handle default branch.
Shift the default branch name to main (or whatever the user has configured).
Add support for antlink rm.
Better error messages when ssh fails.
Additional fixes in antlink mv for subdirs.
Fix release spec and antlink mv for subdirs.
Add test suite and fix more bugs in antlink mv.
Fix runtime bugs in antlink from partial antlink mv.
Release engineering for CentOS.
Bash_completion and preliminary version of antlink mv.
Fixes critical bug in *antlink init* when meta is remote.
First public release.
See the antlink manual page for details.
Why use antlink? Why not use something else (git submodule, git subtree, git annex, Android repo, svn)? Good questions… the short answer is: none of them do things quite right. A much more detailed discussion is in the antlink manual page.