Conversation
There was a problem hiding this comment.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
dangerfile.js:65
- Consider removing unintended extra whitespace and newlines in the fail message string so that the bold and italic parts render consistently across environments. Ensuring a continuous and clean format could help avoid confusion in the message's visual output.
`<b>Please add the Jira issue key at the end of PR title e.g.: #DATA-98</b> (remember to add hash)`
kwaszczuk
force-pushed
the
kwaszczuk/fix-fail-msg
branch
from
327497a to
05bfe1d
Compare
kwaszczuk
force-pushed
the
kwaszczuk/fix-fail-msg
branch
from
05bfe1d to
475461b
Compare
KubaJastrz
approved these changes
Apr 11, 2025
lukaszjaskowski
approved these changes
Apr 11, 2025
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
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.
Error message when no Jira issue key is found is incorrectly formatted due to trailing whitespaces:
Wrapping each line in
<p>tag solves an issue.