fix(reports): update target description to output correctly in markdown #5309
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
9735cd5 to
28b1967
Compare
|
This might not fix it in GitHub, because it looks to do some very deliberate escaping. |
olblak
approved these changes
Jun 3, 2025
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Again in my battle with markdown reports for bitbucket i noticed a bug in the descriptions.
We use
...\n\t* ...throughout the code (here, here and here), this doesn't output correctly in GitHub or Bitbucket (and probably GitLab) but haven't checked.This can be replicated in common mark tester here
GitHub Example
Ref: #5291
Bitbucket Before
Bitbucket After
Test
To test this pull request, you can run the following commands:
Additional Information
Checklist
Tradeoff
Potential improvement