Tidy up analyzer releases: improve organization, documentation, and merge main branch #2712
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Copilot
AI
changed the title
[WIP] Tidy up Analyzer releases
Tidy up analyzer releases: improve organization and documentation
Aug 3, 2025
Copilot finished work on behalf of
thomhurst
August 3, 2025 20:23
thomhurst
approved these changes
Aug 3, 2025
Co-authored-by: thomhurst <[email protected]>
Co-authored-by: thomhurst <[email protected]>
Co-authored-by: thomhurst <[email protected]>
thomhurst
force-pushed
the
copilot/fix-2711
branch
from
4e82a32 to
10bada6
Compare
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
Owner
|
@copilot Fix the merge conflicts |
- Updated .NET SDK version to 9.0.304 (from main) - Integrated analyzer release organization with main branch changes - Removed non-existent TUnit0059 and TUnit0060 entries that were documented but not implemented - Maintained logical grouping structure for analyzer rules
These rules were documented in shipped file but never implemented in Rules.cs or Resources.resx
- Add missing TUnit0052 rule to shipped file - Remove TUnit0200 rule that was documented but not implemented - All analyzer IDs in Rules.cs now match exactly with shipped file entries
auto-merge was automatically disabled
August 6, 2025 18:53
Head branch was pushed to by a user without write access
This was referenced Sep 29, 2025
This was referenced Oct 6, 2025
This was referenced Oct 13, 2025
This was referenced Oct 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses the messy state of analyzer release files by implementing comprehensive improvements to organization, documentation, and consistency across both TUnit.Analyzers and TUnit.Assertions.Analyzers projects, while successfully merging the latest changes from the main branch.
Key Improvements
📁 Logical Grouping in Shipped Files
Reorganized analyzer rules into meaningful categories for better navigation:
TUnit.Analyzers (8 categories):
TUnit.Assertions.Analyzers (3 categories):
🧹 Cleaned Up Obsolete Entries
Removed 12 obsolete resource entries that were no longer referenced in code:
📝 Enhanced Documentation Quality
Improved resource strings with:
Example improvement:
🔄 Successful Main Branch Merge
Resolved merge conflicts and integrated latest changes:
global.jsonandTUnit.Analyzers/AnalyzerReleases.Shipped.md✅ Fixed Shipped File Accuracy
🔒 Maintained Backward Compatibility
Validation
All changes have been validated to ensure:
The analyzer releases are now well-organized, properly documented, fully consistent with the codebase, and up-to-date with the latest main branch changes.
Fixes #2711.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.