chore: resolve template drift vs repo-template (C1, #95)#181
Merged
Conversation
Re-sync the files where this repo had fallen behind the canonical repo-template. Verified locally: src + test Release build clean (0 warnings) and 303/303 tests pass with the analyzer bumps. Synced: - Directory.Build.props: Meziantou.Analyzer 3.0.85->3.0.98, SonarAnalyzer.CSharp 10.25->10.27, Microsoft.SourceLink.GitHub 8.0.0->10.0.300 - codeql.yaml: github/codeql-action init/analyze @V3 -> @v4 - stryker.yaml: full canonical sync (windows-latest so net4x TFMs compile, full SDK matrix, pwsh test-project auto-discovery, umbrella/per-project config modes) — byte-identical to repo-template - benchmarks.yaml: concurrency group -> `gh-pages` (shared cross-workflow group so docfx/release gh-pages publishes don't race) - .gitignore: generalize `_site/` to any depth + ignore auto-generated `docfx_project/api/*.yml` metadata Intentional deviations left as-is (documented in the PR): - benchmarks.yaml "Detect benchmark project" gate — skipped; this repo is the benchmarks reference impl and always has the project present - pr.yaml — template-only self-skip guards; downstream correctly omits them - BannedSymbols.txt / CONTRIBUTING.md — only resolved {{PROJECT_NAME}} placeholders + a correct repo-specific SDK note Closes #95 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Summary
Closes #95 (C1: Resolve template drift).
Ran a per-file drift comparison of every
vNextfile against canonicalrepo-template@mainand re-synced the ones where this repo had fallen behind. Verified locally: src + test Release build clean (0 warnings) and 303/303 tests pass with the analyzer bumps.Synced (repo was behind)
Directory.Build.propscodeql.yamlgithub/codeql-actioninit/analyze@v3→@v4stryker.yamlbenchmarks.yamlgroup:→gh-pages(shared cross-workflow group so docfx/release gh-pages publishes don't race).gitignore_site/to any depth + ignore auto-generateddocfx_project/api/*.ymlIntentional deviations left as-is
benchmarks.yaml"Detect benchmark project" gate — skipped. This repo is the benchmarks reference implementation; the project is always present, so the graceful-no-op gate adds nothing here.pr.yaml— the only diff is template-onlyif: github.repository != 'Chris-Wolfgang/repo-template'self-skip guards; downstream correctly omits them.BannedSymbols.txt/CONTRIBUTING.md— diffs are only resolved{{PROJECT_NAME}}placeholders plus a correct repo-specific SDK requirement.Stacking
Based on
chore/bump-testkit-0.9.0(#177) becausevNext's src does not build cleanly until #177's PublicAPI baseline regeneration lands. Will auto-retarget tovNextonce #177 merges.