{"thread":{"id":"55903","subject":"Server-side-proposed partial clone configuration (default clone --filter option)","startedAt":"2021-06-11T17:39:39Z","lastAt":"2021-06-11T17:39:39Z","messageCount":1,"participants":["Marc Strapetz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"427134","messageId":"f6b3e10e-06b0-fa98-4e34-8a0eeaf45849@syntevo.com","threadId":"55903","inReplyTo":null,"subject":"Server-side-proposed partial clone configuration (default clone --filter option)","fromName":"Marc Strapetz","fromEmail":"marc.strapetz@syntevo.com","sentAt":"2021-06-11T16:40:00Z","receivedAt":"2021-06-11T17:39:39Z","isPatch":false,"sender":{"key":"marc.strapetz@syntevo.com","avatar":"https://avatars.githubusercontent.com/u/3380730?v=4"},"body":" From a (GUI) client perspective, it would be quite helpful to propose \ngood (partial) clone defaults to the user: whether to do a full clone, \nor skip large blobs, ... this can result in much smaller clones by \n*default* and thus a better user experience.\n\nSuch a proposal should most likely be a property of the repository \nitself, for example stored in a specific ref which can efficiently be \nfetched using Git, in preparation of the main clone.\n\nAre there any best practices on how to implement that? Or even better, \nis there any specification on where this meta information should be \nstored, how it should look like, ...? If not, is anyone interested in \nthis topic? I feel that this is something which not every \nplatform/client should reinvent.\n\n-Marc\n"}]}