-
Notifications
You must be signed in to change notification settings - Fork 60.1k
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
Fix inconsistent alerts by using the markdown notation - part 2 #35221
Fix inconsistent alerts by using the markdown notation - part 2 #35221
Conversation
@akordowski Reviewing this now! 💛 |
...ode-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
Outdated
Show resolved
Hide resolved
@akordowski Part 2 approved! ✨ I know we're only halfway through this PR series, but I wanted to relay thanks from the team for this undertaking 💛 I'll have this merged shortly. |
Thank you very much!
No rush! Thank you for your effort to review this big chunks. |
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
As described in the issue #35195 the display of alerts is inconsistent across the documentation.
As the original PR #35216 exceeds the linter limit of 300 files, this PR is part 2 of the changes. It provides changes to alerts across the documentation according to the docs guidelines using the Markdown notation.
What's being changed (if available, include any code snippets, screenshots, or gifs):
Alerts for
note
,tip
,important
andwarning
have been changed and unified from the liquid notation ({% note %}
) to the Markdown notation (> [!NOTE]
) according to the docs guidelines.Check off the following:
I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).
data
directory.For content changes, I have completed the self-review checklist.