Coordinate MSBuild feature changes behind opt-out Change Waves.
npx skills add https://github.com/dotnet/dotnet --skill changewaves
Please help me install this Agent Skill. Skill: changewaves Source: https://github.com/dotnet/dotnet/tree/main/src/msbuild/.github/skills/changewaves Command: npx skills add https://github.com/dotnet/dotnet --skill changewaves
Change waves provide a safe, temporary opt-out mechanism to group risky feature changes, reducing production-risk by enabling controlled rollout and rollback.
Add a new wave entry for the target version and wrap the affected code with AreFeaturesEnabled checks.
High-intent search queries and answers about installing and using this skill.
MSBuild change waves are a temporary opt-out mechanism that groups risky feature changes to enable controlled rollout and rollback, minimizing production compatibility risk across the codebase.
You can gate MSBuild code paths by wrapping affected features with AreFeaturesEnabled checks, ensuring users can opt out of risky changes during compatibility periods.
To create a change wave, add a new version entry in ChangeWaves.cs, wrap the affected code with AreFeaturesEnabled checks, add tests, and document the entry in ChangeWaves.md and ChangeWaves-Dev.md.
Yes, the MSBuild change wave process requires documenting new entries and retirements in ChangeWaves.md and ChangeWaves-Dev.md to keep teams aligned on evolving features.
You should retire expired MSBuild change waves through a clear rotation process, documenting the retirement in ChangeWaves.md and ChangeWaves-Dev.md to maintain alignment.
Luohao-YanPromote feature flags through staged environments in the Warp codebase.
Sheldon-92Execute test suites and report failures with coverage metrics.
cfardevModify use case markdown files and synchronize roadmap status.
terzigoluAdd a feature flag to Cargo.toml and the FeatureFlag enum for runtime gating.
