Skip to content

Enable several recently added analyzers #116881

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.

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
merged 1 commit into from
Jul 1, 2025

Conversation

stephentoub
Copy link
Member

No description provided.

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This pull request enables several recently added analyzers. It updates regex matching logic in linker XML processing files to use Regex.IsMatch, inserts logging code blocks in multiple hosting lifetime implementations, and revises analyzer settings in the global configuration.

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file
File Description
src/tools/illink/src/linker/Linker.Steps/ProcessLinkerXmlBase.cs Replaces regex.Match(...).Success with regex.IsMatch for improved clarity.
src/libraries/Microsoft.Extensions.Hosting/src/Internal/ConsoleLifetime.cs Wraps logging calls within a new if block in OnApplicationStarted.
src/libraries/Microsoft.Extensions.Hosting.WindowsServices/src/WindowsServiceLifetime.cs Adds braces to enclose logging within the ApplicationStarted registration.
src/libraries/Microsoft.Extensions.Hosting.Systemd/src/SystemdLifetime.cs Similar update to enclose logging calls within a conditional block.
src/coreclr/tools/Common/Compiler/ProcessLinkerXmlBase.cs Replaces regex.Match(...).Success with regex.IsMatch for consistent behavior.
eng/CodeAnalysis.src.globalconfig Updates analyzer comments and enables additional analyzers with new severities.

@github-actions github-actions bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jun 20, 2025
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Jun 20, 2025
@teo-tsirpanis teo-tsirpanis added area-Meta and removed linkable-framework Issues associated with delivering a linker friendly framework needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Jun 21, 2025
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Jun 21, 2025
@stephentoub stephentoub force-pushed the enablemoreanalyzers branch from 483447c to 3b73682 Compare June 22, 2025 01:59
@stephentoub stephentoub force-pushed the enablemoreanalyzers branch from 3b73682 to bfc530b Compare June 24, 2025 12:51
@stephentoub stephentoub removed the linkable-framework Issues associated with delivering a linker friendly framework label Jun 25, 2025
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Jun 25, 2025
@stephentoub stephentoub removed the linkable-framework Issues associated with delivering a linker friendly framework label Jun 30, 2025
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Jun 30, 2025
@stephentoub stephentoub force-pushed the enablemoreanalyzers branch from bfc530b to d10159e Compare June 30, 2025 15:09
@stephentoub stephentoub merged commit 61f2ad6 into dotnet:main Jul 1, 2025
160 of 166 checks passed
@stephentoub stephentoub deleted the enablemoreanalyzers branch July 1, 2025 01:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Meta linkable-framework Issues associated with delivering a linker friendly framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants