Fix linter issues with ReadMe #4455
Merged
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
|
Thanks Nirmal4G for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌 |
ghost
requested review from
Arlodotexe
approved these changes
Jan 11, 2022
Aligns with the rest of the titles
Always use markdown format if possible. This format to represent image with a link is supported by most markdown parsers.
Nirmal4G
force-pushed
the
hotfix/readme
branch
from
395372a to
632fad0
Compare
zateutsch
approved these changes
Jan 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Contributes to #4068
Rest of the titles have emojis, why not this? So, I used Champion Cup (
🏆) emoji.The format to represent image with a link is supported by most markdown parsers:
[](info-link).PR Type
What kind of change does this PR introduce?
What is the current behavior?
My markdown linter reports issues with in-line HTML.
What is the new behavior?
Made sure that we convert the in-line HTML to markdown format.
PR Checklist
Please check if your PR fulfills the following requirements:
Other information
Squash merge if possible.