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
This happens when GitHub previews Markdown files like README.md and similar but does not happen here in issues, for example, this is how it renders:
one
two
Is there an official spec on how GitHub treats user text written as comments to issues and pull requests? Is it fair to say that GH issues and comments are not GFM since they behave differently from the spec?
The text was updated successfully, but these errors were encountered:
I swear it used to be documented as a part of GFM pre-CommonMark, but I really can't find such a mention now. Heck, I don't even know whether this library is the exact one they use in the backend...
According to GFM spec on hard line breaks, this Markdown:
should render as:
This happens when GitHub previews Markdown files like
README.md
and similar but does not happen here in issues, for example, this is how it renders:one
two
Is there an official spec on how GitHub treats user text written as comments to issues and pull requests? Is it fair to say that GH issues and comments are not GFM since they behave differently from the spec?
The text was updated successfully, but these errors were encountered: