Skip to content

ci(nullable-gate): use /t:Rebuild so the nullable gate is actually enforced #361

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
1 commit merged into from
Jul 20, 2026
Merged

ci(nullable-gate): use /t:Rebuild so the nullable gate is actually enforced #361

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,13 @@ jobs:
- name: Build with nullable warnings treated as errors
shell: pwsh
run: |
& msbuild $env:SOLUTION_PATH /t:Build /m /p:Configuration=Debug `
# Use /t:Rebuild (not /t:Build) so this step always performs a genuine full
# recompile under /p:Nullable=enable. The preceding "Build with analyzers"
# step already compiled everything under the projects' own Nullable settings;
# MSBuild's incremental up-to-date check does not invalidate on a changed
# -p:Nullable command-line property alone, so a plain /t:Build here would
# silently skip recompilation and never actually enforce this gate.
& msbuild $env:SOLUTION_PATH /t:Rebuild /m /p:Configuration=Debug `
"/p:Platform=Any CPU" `
/p:Nullable=enable /p:TreatWarningsAsErrors=true
if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }
Expand Down
Loading