Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Design a template for the code analysis rules used in WinForms #1939

Open
adegeo opened this issue Nov 19, 2024 · 0 comments
Open

Design a template for the code analysis rules used in WinForms #1939

adegeo opened this issue Nov 19, 2024 · 0 comments
Assignees
@adegeo
Labels
Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Label to indicate an item has been imported.

Comments

@adegeo
Copy link
Contributor

adegeo commented Nov 19, 2024 •
edited by sequestor bot
Loading

This can apply to WPF

I published a PR that documented some new code rules (#1938) which used the C# code error documentation as a template. However, I think perhaps the style used in https://github.com/dotnet/docs/blob/main/docs/fundamentals/code-analysis/style-rules/ide0002.md might be better.

This issue is to track work related to designing a new issue template and updating the existing error/warning docs to follow it.

By creating an issue template, we can use AI automation to help generate the articles from the GitHub issue, like we do with breaking changes docs.

Associated WorkItem - 360642
@adegeo adegeo self-assigned this Nov 19, 2024
@issues-automation issues-automation bot added the Pri3 Low priority label Nov 19, 2024
@dotnetrepoman dotnetrepoman bot added the ⌚ Not Triaged Not triaged label Nov 19, 2024
@adegeo adegeo added Pri1 High priority, do before Pri2 and Pri3 🗺️ reQUEST Trigger label to import an issue into Quest and removed Pri3 Low priority labels Nov 19, 2024
@dotnetrepoman dotnetrepoman bot added 🗺️ mapQUEST Only used as a way to mark an issue as updated. RepoMan should instantly remove it. and removed ⌚ Not Triaged Not triaged 🗺️ mapQUEST Only used as a way to mark an issue as updated. RepoMan should instantly remove it. labels Nov 19, 2024
@adegeo adegeo moved this from 🔖 Ready to Slipped in dotnet/docs December 2024 Sprint Jan 7, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated. RepoMan should instantly remove it. label Jan 7, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated. RepoMan should instantly remove it. label Jan 7, 2025
@sequestor sequestor bot added 📌 seQUESTered Label to indicate an item has been imported. and removed 🗺️ reQUEST Trigger label to import an issue into Quest labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adegeo adegeo

Labels
Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Label to indicate an item has been imported.
Projects
dotnet/docs December 2024 Sprint
Status: Slipped
dotnet/docs January 2025 sprint project
Status: 🔖 Ready
Milestone
No milestone
Development

No branches or pull requests
1 participant
@adegeo