From b81501acf4bc0e9067b892abd5ee3f4649633475 Mon Sep 17 00:00:00 2001
From: vanzue <vanzue@outlook.com>
Date: Sat, 31 Jan 2026 14:37:41 +0800
Subject: [PATCH] fix(build): use case-insensitive comparison for BuildTests
 property

YAML boolean parameters resolve to 'True'/'False' (Pascal case), but the
original condition checked for lowercase 'false' only. This caused the
skip logic to not work correctly in CI/release pipelines.

Using .ToLower() ensures the comparison works regardless of case.
---
 Directory.Build.props | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Directory.Build.props b/Directory.Build.props
index 9f5e65e00f..6f7e00afff 100644
--- a/Directory.Build.props
+++ b/Directory.Build.props
@@ -25,8 +25,9 @@
     Match: projects ending in Test, Tests, UnitTests, UITests, FuzzTests, or in a folder named Tests.
     Also matches projects starting with UnitTests- (e.g., UnitTests-CommonLib).
     Also removes all PackageReference/ProjectReference to prevent NuGet restore and dependency builds.
+    Note: Using case-insensitive comparison for BuildTests (handles 'false', 'False', 'FALSE').
   -->
-  <PropertyGroup Condition="'$(BuildTests)' == 'false'">
+  <PropertyGroup Condition="'$(BuildTests.ToLower())' == 'false'">
     <_ProjectName>$(MSBuildProjectName)</_ProjectName>
     <!-- Match any project ending with "Test" or "Tests" (covers UnitTests, UITests, FuzzTests, etc.) -->
     <_IsSkippedTestProject Condition="$(_ProjectName.EndsWith('Test'))">true</_IsSkippedTestProject>