@@ -162,7 +162,7 @@ In order for the sources of the new repo to by synchronized into the VMR, the
162
162
repo needs to be registered in the [`source-mappings.json`
163
163
file](https://github.com/dotnet/dotnet/blob/main/src/source-mappings.json) which
164
164
tells the tooling where from and which sources should be synchronized. Please
165
- open a PR in [`dotnet/sdk `](https://github.com/dotnet/dotnet) and add
165
+ open a PR in [`dotnet/dotnet `](https://github.com/dotnet/dotnet) and add
166
166
your repository into `src/source-mappings.json`.
167
167
168
168
# ## Cloaking (filtering) the repository sources
@@ -180,10 +180,7 @@ is needed for the source-built .NET scenario.
180
180
181
181
# # Validate
182
182
183
- Once the downstream dependency(s) are added to the new repo and those changes
184
- flow into `dotnet/sdk`, a complete .NET product can be built from source.
185
- The repository will be synchronized into the VMR during the first build and the
186
- VMR will be built. This will validate that no prebuilts were added to the system
187
- and everything is functioning correctly. Please notify
188
- [@source-build](https://github.com/orgs/dotnet/teams/source-build)
189
- to be on the lookout for the new repo and they will validate as necessary.
183
+ Once the code flows to the VMR, the PR validation legs will ensure that no
184
+ [prebuilts](https://github.com/dotnet/source-build/blob/main/Documentation/eliminating-pre-builts.md#what-is-a-prebuilt)
185
+ were added to the system and everything is functioning correctly.
186
+ If you need help on addressing any prebuilds, reach out to @source-build.
0 commit comments