Inspired by go-git, we should create our own compatibility documentation. Likely two tables, one for Git and another for git-lfs
Known incompatibilities:
- note refs (but is supported by go-git, so potentially in the future)
- ???
The idea here is to quickly show users the limitations of our remote helpers. The end goal is to support at least the common use cases: push, fetch, tag, clone, etc. However Git with its extensive capabilities has many edge cases, such as sha256 repository formats (see gnoci issue). A compatibility table would allow advanced users to quickly see if their use cases are supported.
It should be noted that not all features of Git are applicable to us, e.g. git init, we're mostly concerned with actions that involve a (OCI) remote.
Inspired by
go-git, we should create our own compatibility documentation. Likely two tables, one for Git and another for git-lfsKnown incompatibilities:
The idea here is to quickly show users the limitations of our remote helpers. The end goal is to support at least the common use cases: push, fetch, tag, clone, etc. However Git with its extensive capabilities has many edge cases, such as sha256 repository formats (see gnoci issue). A compatibility table would allow advanced users to quickly see if their use cases are supported.
It should be noted that not all features of Git are applicable to us, e.g.
git init, we're mostly concerned with actions that involve a (OCI) remote.