Add In-Memory Repository Support

Commencez par examiner le contrat IRepository et l’implémentation Repository, puis vérifiez quelle prise en charge libgit2 fournit pour les dépôts qui n’utilisent pas le système de fichiers. Définissez l’abstraction nécessaire pour les datastores en mémoire et les autres datastores non basés sur des fichiers, en démontrant l’achèvement par le bon fonctionnement d’opérations de dépôt telles que clone, create et push sans accès direct au disque.

I am building an application that needs to interact with git (clone repo, create repo, push, etc.) but does not have direct access to a disk. I would like to be able to work with a git repo entirely in-memory.

As an aside, I would also like to be able to work with a git repository that is written out to a non-file datastore such as a database.

In general, it would be nice if the logic in Repository was abstracted out away from the disk. It appears that IRepository is not tightly coupled with disk (assuming all of the various methods that take a path are referring to a relative path). However, there appears to be quite a bit of git specific logic bound up in the Repository implementation which makes it difficult to a novice contributor to implement a custom datastore engine (e.g., in-memory, database, etc.).

Researching this topic very briefly, it appears that the underlying libgit2 supports non-filesystem repositories, so I don't believe this is a technical limitation with libgit2.