You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it should output without the extra backtick so it renders like this
to add the following reviewers johnlock
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Afer looking more closely, this happens anytime using add-comment@v1 cause it seems to assume a short single-line comment like
add comment foo bar baz
but if you do a multi-line comment, like the explainRankByGitBlame dump, then you get a leading backtick as well before the comment and that tailing one causing mis-formatting
can see the leading one here:
it would probably be better to have add-comment@v1 start the comment on the next line and not add any of its own formatting in dry run
The text was updated successfully, but these errors were encountered:
michaeldrotar
changed the title
Extra backtick causing format issues in dry run output
add-comment@v1 backticks causing format issues in dry run output
Mar 13, 2023
I have an update to share on this. Our roadmap contains plans to rework gitStream testing capabilities over the next couple of months, and this will be either fixed or reworked as part of that initiative. Stay tuned!
Describe the bug
There's an extra backtick here:
![image](https://user-images.githubusercontent.com/820263/224717172-17f21fa4-13c6-4dc5-9f12-08eb0943b1a2.png)
![image](https://user-images.githubusercontent.com/820263/224717284-adbb1797-c29f-4bdc-aa8a-2e9c7a75c862.png)
which misformats here
it should render like this
To Reproduce
Steps to reproduce the behavior:
Expected behavior
it should output without the extra backtick so it renders like this
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Afer looking more closely, this happens anytime using
add-comment@v1
cause it seems to assume a short single-line comment likefoo bar baz
but if you do a multi-line comment, like the
explainRankByGitBlame
dump, then you get a leading backtick as well before the comment and that tailing one causing mis-formattingcan see the leading one here:
it would probably be better to have
add-comment@v1
start the comment on the next line and not add any of its own formatting in dry runThe text was updated successfully, but these errors were encountered: