You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sparse checkout allows you to choose which parts of a repository you want to download, instead of downloading everything.
68
-
Next you have to specify filters for sparse checkout to use (stored in `.git/info/sparse-checkout`).
68
+
In the previous step, `--filter=blob:none` means that the commit history has not been downloaded yet, and `--no-checkout` means that no files have been added to the working copy (the index) yet.
69
69
70
-
You must add your manifest files to the repository in the following folder structure:
71
-
To initialize sparse checkout for a repository you must type:
70
+
Before downloading anything, you'll have to specify filters for sparse checkout to use (stored in `.git/info/sparse-checkout`).
71
+
72
+
First, here is an explanation of what is going to be set up. You must add your manifest files to the repository in the following folder structure:
@@ -82,24 +83,26 @@ The `PackageIdentifier` and the `PackageVersion` values in the manifest must mat
82
83
83
84
Thus to set up sparse checkout for all manifests of a publisher, you'd type:
84
85
85
-
1. If you are using Git version 2.37.0 or newer, run the following command to set up sparse checkout for your folder.
86
+
* If you are using Git version 2.37.0 or newer, run the following command to set up sparse checkout for your folder.
86
87
87
88
```powershell
88
89
git sparse-checkout set manifests\<letter>\<publisher>
89
90
```
90
91
91
-
If you are using an older version of Git, refer to the [Git documentation](https://git-scm.com/docs/git-sparse-checkout) for how to set up sparse checkout for your local repository.
92
+
* If you are using an older version of Git, refer to the [Git documentation](https://git-scm.com/docs/git-sparse-checkout) for how to set up sparse checkout for your local repository.
92
93
93
94
Note that the above command will override all current sparse checkout settings and set it up for only that one folder, refer to the [Git documentation](https://git-scm.com/docs/git-sparse-checkout) for setting up sparse checkout with multiple folders.
94
95
95
96
### Step 5: Checkout the repository
96
97
97
-
You can now apply the sparse checkout settings by running.
98
+
You can now apply the sparse checkout settings by running the normal checkout command.
98
99
99
100
```powershell
100
101
git checkout
101
102
```
102
103
104
+
Even if the folder you want to submit hasn't been committed to the repository yet, you must still run the checkout command, as it will be impossible to add (and thus commit) anything without the Git internals it sets up (the index).
105
+
103
106
If you are entering multiple submissions, create a branch instead of a fork. We currently allow only one manifest file per submission.
104
107
105
108
```powershell
@@ -145,7 +148,7 @@ If there is ever an error during the process, you will be notified and our label
145
148
146
149
## Validation process
147
150
148
-
When you [create a pull request](#step-6-create-a-pull-request) to submit your manifest to the Windows Package Manager repository, this will start an automation process that validates the manifest and processes your pull request. GitHub labels are used to share progress and allow you to communicate with us.
151
+
When you [create a pull request](#step-8-create-a-pull-request) to submit your manifest to the Windows Package Manager repository, this will start an automation process that validates the manifest and processes your pull request. GitHub labels are used to share progress and allow you to communicate with us.
0 commit comments