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
I have noticed that Sapling (via ISL) is stripping trailing new lines in my commit body. This isn't a major functional problem, but on GitHub because of markdown formatting, the last sentence in the body becomes a heading due to the --- immediately after it. This makes the PR body look quite comical (eg look at facebook/react#31384 prior to my edit) since the whole thing becomes an H2.
You can work around this by adding any non-whitespace character to the end of your description, or manually editing your PR description after it's opened, but it'd be better if Sapling just didn't strip trailing whitespace in commit bodies to begin with.
The text was updated successfully, but these errors were encountered:
I have noticed that Sapling (via ISL) is stripping trailing new lines in my commit body. This isn't a major functional problem, but on GitHub because of markdown formatting, the last sentence in the body becomes a heading due to the
---
immediately after it. This makes the PR body look quite comical (eg look at facebook/react#31384 prior to my edit) since the whole thing becomes an H2.You can work around this by adding any non-whitespace character to the end of your description, or manually editing your PR description after it's opened, but it'd be better if Sapling just didn't strip trailing whitespace in commit bodies to begin with.
The text was updated successfully, but these errors were encountered: