Canonical sync (protected files) ahead of v0.3.2#202
Merged
Conversation
Extracts the protected-file deltas from vNext (Release v0.3.2 PR #166) so that PR can merge through the standard ruleset rather than admin- bypassing the entire 34-file diff (which would also waive required_review_thread_resolution on every non-protected file). Files in this PR (matching the `Detect .NET Projects` guard patterns): - .editorconfig - BannedSymbols.txt - Directory.Build.props - .github/workflows/benchmarks.yaml - .github/workflows/codeql.yaml - .github/workflows/pr.yaml - .github/workflows/release.yaml - .github/workflows/stryker.yaml These carry the canonical CI/analyzer/banned-API updates folded into v0.3.2 (C1 fleet template-drift sync, CI2 github-actions ecosystem, A1 PublicApiAnalyzers scaffolding, T3 Stryker workflow, D6 versions preservation guard, D8 inline root redirect, etc.). They are verbatim copies of vNext's content at the time of extraction; no new edits. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why this PR exists
The Release v0.3.2 PR (#166) has 34 files in its diff, 8 of which are "protected" under
pr.yaml'sDetect .NET Projectsguard. Merging #166 as-is would require admin-bypass on the whole 34-file diff — and the bypass waives every ruleset rule at once, includingrequired_review_thread_resolutionon the 26 non-protected files.This split-out PR carries only the 8 protected files so the bypass surface is small and easy to eyeball. #166 then merges through the standard ruleset with full review-thread enforcement.
What's in here
.editorconfig.editorconfigis exact-match protected — controls analyzer rules and code styleBannedSymbols.txtProcess.Start("rm")past CIDirectory.Build.props.github/workflows/benchmarks.yaml.github/workflows/codeql.yaml.github/workflows/pr.yaml.github/workflows/release.yaml.github/workflows/stryker.yamlThese are verbatim copies of vNext's content. No edits applied during extraction —
git difffrom origin/main shows exactly the deltas already on vNext.Expected CI behaviour
Detect .NET Projects→ ❌ FAIL (expected — that's why we're splitting)detect-projects.outputs.has-projects)Merge plan
origin/mainback intovNext— the protected-file delta on #166 vanishes.MERGEABLEwith full ruleset enforcement.Same shape as
This is the standard split done previously for DateTime-Extensions v0.X via
protected/add-benchmarks-yamland the same pattern lined up for ETL-Test-Kit #112 / ETL-Abstractions #192 / ETL-FixedWidth #134.