threads / discuss / 55903

Server-side-proposed partial clone configuration (default clone --filter option)

Subject: Server-side-proposed partial clone configuration (default clone --filter option)

## tl;dr

One message between Jun 11, 2021 and Jun 11, 2021.

replies: 0people: 1as markdown or json

Marc Strapetz· Jun 11, 2021, 16:40 UTC · lore
 From a (GUI) client perspective, it would be quite helpful to propose 
good (partial) clone defaults to the user: whether to do a full clone, 
or skip large blobs, ... this can result in much smaller clones by 
*default* and thus a better user experience.

Such a proposal should most likely be a property of the repository itself, for example stored in a specific ref which can efficiently be fetched using Git, in preparation of the main clone.

Are there any best practices on how to implement that? Or even better, is there any specification on where this meta information should be stored, how it should look like, ...? If not, is anyone interested in this topic? I feel that this is something which not every platform/client should reinvent.

-Marc

← back to recent threads