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

XS✔ ◾ CodeAuditor - Fix broken link #7947

Merged
merged 3 commits into from
Feb 14, 2024
Merged

XS✔ ◾ CodeAuditor - Fix broken link #7947

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
63faebe
CodeAuditor - Fix broken link
tombui99 Feb 14, 2024
3cb3fc2
Auto-fix Markdown files
github-actions[bot] Feb 14, 2024
fe16248
Update rule.md
tiagov8 Feb 14, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions rules/do-you-know-how-to-laser-in-on-the-smelliest-code/rule.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,6 @@ redirects: []

Rather than randomly browsing for dodgy code, use Visual Studio's Code Metrics feature to identify "Hot Spots" that require investigation.


::: bad
![Figure: The bad was is to browse the code](lotto-balls.jpeg)
:::
Expand All @@ -33,12 +32,9 @@ Rather than randomly browsing for dodgy code, use Visual Studio's Code Metrics f
Identifying the problem areas is only the start of the process. From here, you should speak to the developers responsible for this dodgy code. There might be good reasons why they haven't invested time on this.

![Figure: Find out who the devs are by using CodeLens and start a conversation](codelens-start-conversation.png)
**Tip:** To learn how to use Annotate, see [Do you know the benefits of Source Control?](http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterSourceControlwithTFS.aspx#UsingSourceControl)



**Tip:** Learn [the benefits of Source Control](/do-you-know-the-benefits-of-using-source-control).

::: greybox
**Suggestion to Microsoft:** allow us to visualize the developers responsible for the bad code (currently and historically) using CodeLens.

**Suggestion to Microsoft:** Allow us to visualize the developers responsible for the bad code (currently and historically) using CodeLens.
:::
Loading