fix(content): Fix warnings markdown on release notes - #522
Merged
Conversation
Signed-off-by: Michalis Pappas <michalis@unikraft.io>
michpappas
force-pushed
the
fix_warning_markdown
branch
from
September 12, 2025 10:26
78e7bb2 to
f35907e
Compare
nderjung
approved these changes
Sep 12, 2025
nderjung
left a comment
nderjung
left a comment
Member
There was a problem hiding this comment.
Thanks!
Reviewed-by: Alexander Jung alex@unikraft.com
Approved-by: Alexander Jung alex@unikraft.com
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The markdown currently used for warnings seems to be GitHub specific. Switch to the syntax used in https://github.com/unikraft/docs/blob/main/content/releases/v0.17.0.mdx. For rendered output see: https://unikraft.org/releases/v0.17.0.