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
It seems that GitHub, for user convenience, automatically parses regular line breaks as hard line breaks in issues, discussion and pull request comments (see https://github.com/orgs/community/discussions/16925?sort=new#discussioncomment-6507284). For repository markdown files, however, these regular line breaks are parsed as soft line breaks. Although I understand it is impossible to align this behaviour among markdown issues, discussion, and pull request comments. We should document them on https://github.github.com/gfm/ under the Soft line breaks section. Something like
Note
For user convenience in Github issues, pull requests and discussion comments, regular line breaks are automatically replaced by hard line breaks.
I'm happy to create a pull request but I couldn't find where and how this documentation is created.
It's not something they do in their markdown parser as far as I understand , and there are many many other features like that, which they do on issues/prs/discussions/comments, which are already (sparsely) documented in their regular docs (https://docs.github.com/en/get-started/writing-on-github)
It's not something they do in their markdown parser as far as I understand , and there are many many other features like that, which they do on issues/prs/discussions/comments, which are already (sparsely) documented in their regular docs (https://docs.github.com/en/get-started/writing-on-github)
It seems that GitHub, for user convenience, automatically parses regular line breaks as hard line breaks in issues, discussion and pull request comments (see https://github.com/orgs/community/discussions/16925?sort=new#discussioncomment-6507284). For repository markdown files, however, these regular line breaks are parsed as soft line breaks. Although I understand it is impossible to align this behaviour among markdown issues, discussion, and pull request comments. We should document them on https://github.github.com/gfm/ under the Soft line breaks section. Something like
I'm happy to create a pull request but I couldn't find where and how this documentation is created.
Related to
The text was updated successfully, but these errors were encountered: