Protected config for v0.8.1 release: protected-only PR ahead of #112#162
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jun 26, 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.
Protected-only PR extracted from the v0.8.1 release branch (vNext, #112) so the larger release diff merges through full ruleset enforcement instead of an all-or-nothing admin bypass.
Same pattern as ETL-Abstractions #231.
Protected files
.editorconfig.github/workflows/codeql.yaml,pr.yaml,release.yaml,stryker.yamlBannedSymbols.txtDirectory.Build.propsExpected CI
Detect .NET Projects❌ — expected; admin-bypass merge after reviewing the diff.After merge
Merge
mainback intovNextso #112's protected-file delta vanishes and it becomes mergeable without bypass.Follows: #112