Access via git

In addition to ordinary release downloads, some projects' latest releases are accessible by cloning a git repository. This is indicated by a "Accessible via git" note on the project's home page, and is designed to simplify addon developer workflows involving updating embedded libraries.

This functionality is experimental and liable to change.

Git repository URLs

The git repository URL is derived from the project's home page address, replacing /addons/ with /addons.git/.

Example

Home URL: https://www.townlong-yak.com/addons/bearfacts
 Git URL: https://www.townlong-yak.com/addons.git/bearfacts

Shallow clones will fail

Note that explicitly requesting git to perform a shallow clone (using e.g. git clone --depth 1) will fail because the repositories are served using a dumb HTTP transport.

In principle, there is no need to perform a shallow clone in this fashion, as these repositories do not provide excess history.

When using the release.sh packager

To avoid failures due to attempting a shallow clone, specify commit: default in addition to the repository URL in the .pkgmeta file. This will checkout the default branch, and is equivalent to what you would get when cloning the base URL.

.pkgmeta example

externals:
  SuperCat/libs/BearFacts:
    url: https://www.townlong-yak.com/addons.git/bearfacts
    commit: default