-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix release markdown rendering of double newlines #69
Comments
Interesting, and I assume this only happens because you don't group by labels 🤔 . Let me see, this should be fairly easy to fix. |
yeah, I don't have any labels in the project i was thinking if you out of ideas what to put between lists, perhaps a |
Could be, but I also like the |
Refs: #69 Drops usage of older version of `ocramius/package-versions`
This label, when set, will function as a fallback for any items that are not grouped by any label. Refs: #69
This label, when set, will function as a fallback for any items that are not grouped by any label. Refs: #69
@WyriHaximus once it's merged and released I have to motivate laminas guys. so if it's enabled by default it would be easier for me :D |
@glensc The only issue with enabling it by default is that would be a backward compatibility break, and that I don't have a good default word. |
@glensc Jumped into that issue, let's see :) |
Created laminas/automatic-releases#177. the text will appear before the pr/issue list? |
It is treated like any other label. |
Originally posted to laminas/automatic-releases#176
Because there's a double newline between two lists, markdown renders every item with double newlines and considers the two lists as one.
The workaround is to put some non-list element(s) between the lists.
Current behavior
markdown source
Expected behavior
markdown source
The text was updated successfully, but these errors were encountered: