Open EugeneDraitsev opened 3 years ago
Oh, I figured a workaround for it
This dangerfile.js
will generate 1 correct and 1 broken markdown message:
import { markdown } from "danger"
markdown('## this is not working')
markdown('\n## now it works')
So, the issue is that you need to add leading \n
to all markdown strings for bitbucket cloud
Good digging
Describe the bug
I have a super simple
dangerfile.js
I expect to see h2 markdown in my danger comment in PR, bit I have this:
To Reproduce Steps to reproduce the behavior:
dangerfile.js
file as described above at bitbucket cloud repoExpected behavior Markdown works fine
Screenshots Screenshot attached above. You also can have a look to PR
Your Environment