dotnet-ci-benchmarking

You can gate CI on performance regressions by comparing BenchmarkDotNet JSON exports against a baseline with configurable percentage thresholds. This Skill automates the detection process and alerts you if a code change degrades performance beyond the set threshold.

Manage benchmark baselines in GitHub Actions by utilizing workflow artifacts to store and retrieve previous results. This Skill automates baseline file management, ensuring reliable comparisons against the main branch during continuous integration runs.

Yes, CI benchmarking with this Skill requires BenchmarkDotNet v0.14 or higher. This version dependency is necessary to support the JSON export functionality used for comparing performance results against your stored baseline.

Automating performance regression detection in .NET is best achieved by comparing current benchmark results against a baseline with defined threshold alerts. This Skill handles the automated threshold checks and baseline tracking directly within your CI pipeline.

Yes, you can track performance trends over time by managing baseline benchmark results through GitHub Actions artifacts. This Skill provides the foundation for trend reporting by storing and comparing historical benchmark data across pipeline runs.

You need performance regression testing in your CI pipeline when you want to prevent code changes from inadvertently slowing down critical APIs. It ensures that new merges do not degrade application performance compared to the main branch baseline.