-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Markdown output appears to not render nicely on Github #734
Comments
Hey @nuxeh, thank you for providing the issue! Do you mind opening a PR for that fix? We might change it to something like:
WDYT? |
Sure thing, I'm just not sure about how to integrate such a change, so what do you think would be the best way trigger this new type of output? A command line option, in the configuration? I think either could work, potentially. But yes, agree on the format, however I'd also propose adding nested bullets to preserve the long descriptions as separate paragraphs, rather than being merged into the main change heading. And as a small thing, i think I prefer it slightly without the
Which looks like: Unreleased (2020-12-08):
|
Oh yeah the format makes sense to me. Yes making it an CLI option would probably a good move forward, not sure how to name such a flag. |
Would |
Yeah I think it would. 👍 |
e.g.:
While this seems like nice compact markdown, the description paragraphs get rendered in the same line as the change heading, something like this:
The text was updated successfully, but these errors were encountered: