moq-analyzers-change-control

Enforcing change control for a Roslyn analyzer repository involves categorizing changes, validating required gate checks like CI builds and tests, and managing dependencies. This minimizes release-breaking risks and ensures stable package releases.

Required gate checks for modifying code analysis rules include CI builds, tests, Codacy quality checks, and performance benchmarks. These gates validate that changes meet quality standards before being merged into the analyzer package.

Changes for a .NET Roslyn analyzer are classified as New Rule, Rule Behavior Change, Code Fix, Shared-Helper Change, Dependency Change, CI/Workflow Change, Docs Only, or Release Promotion. Proper classification ensures the correct quality gates are applied.

Yes, the change control process enforces dependency management rules for bundled dependencies, build-time analyzers, and test frameworks. This validation ensures that dependency modifications do not destabilize the Roslyn analyzer package.

Yes, you can manage CI/workflow changes and release promotions by categorizing them under specific change types. The process validates these modifications against required gates to maintain quality standards during releases.

The best way to prevent release-breaking issues is to enforce strict change control and quality standards. By validating dependency management and applying necessary gate checks for each change type, maintainers ensure stable releases.