@@ -27,36 +27,9 @@ on the client is at least the same as on the server (or later). Login to
27
27
Gitea server as admin and head to Site Administration -> Configuration to
28
28
see Git version of the server.
29
29
30
- By default, clone filters are disabled, which cause the server to ignore
31
- ` --filter ` option .
30
+ By default, clone filters are enabled, unless ` DISABLE_PARTIAL_CLONE ` under
31
+ ` [git] ` is set to ` true ` .
32
32
33
- To enable clone filters on per-repo basis, edit the repo's ` config ` on
34
- repository location. Consult ` ROOT ` option on ` repository ` section of
35
- Gitea configuration (` app.ini ` ) for the exact location. For example, to
36
- enable clone filters for ` some-repo ` , edit
37
- ` /var/gitea/data/gitea-repositories/some-user/some-repo.git/config ` and add:
38
-
39
- ``` ini
40
- [uploadpack]
41
- allowfilter = true
42
- ```
43
-
44
- To enable clone filters globally, add that config above to ` ~/.gitconfig `
45
- of user that run Gitea (for example ` git ` ).
46
-
47
- Alternatively, you can use ` git config ` to set the option.
48
-
49
- To enable for a specific repo:
50
-
51
- ``` bash
52
- cd /var/gitea/data/gitea-repositories/some-user/some-repo.git
53
- git config --local uploadpack.allowfilter true
54
- ```
55
- To enable globally, login as user that run Gitea and:
56
-
57
- ``` bash
58
- git config --global uploadpack.allowfilter true
59
- ```
60
33
61
34
See [ GitHub blog post: Get up to speed with partial clone] ( https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/ )
62
35
for common use cases of clone filters (blobless and treeless clones), and
0 commit comments