"Reply to this email directly" includes email thread/history #77491
Replies: 9 comments
-
|
This is even worse when you view the issue within a project. It strips out all newlines etc so it is just a jumbled mess. It is at least readable when you view the issue in whatever repo it lives in. Not to mention the fact that the history grows with every comment and ends up having redacted emails everywhere, multiple links to the issue (which makes no sense since it is now in a comment on the issue itself), "unsubscribe from notifications" links, and socials links or other poorly parsed junk from email signatures. This just needs to be turned off completely |
Beta Was this translation helpful? Give feedback.
-
|
Added a related suggestion: https://bettersoftwaresuggestions.com/github/help-me-have-a-clean-message-when-replying-to-an-issue-via-email/ |
Beta Was this translation helpful? Give feedback.
-
|
Comments from email are just an absolute mess. Is there any way around this? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, the "Reply to this email directly" used to work fine for me, but now (for the past few months), it includes the whole thread and renders the full text as HTML, including things like
Is this possibly related to changes to Issues in https://github.com/orgs/community/discussions/148713? |
Beta Was this translation helpful? Give feedback.
-
|
I want to add that this does not work at all if the email client is not in English. Here is an instance of that happening to me. Since my email client (Android gmail in this case) is in Portuguese, it completely fails to parse the email history and it just gets included in the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Tried replying to an issue via email for the first time and saw that it included the full "On [date], [email] wrote:" text in the thread. GitHub also stripped out the spacing, so my message got merged awkwardly—kind of like when a food label smashes all the ingredients into one unreadable line. Plus, I couldn’t use markdown when editing on the web. Would be great if reply history was auto-trimmed and markdown was enabled for web edits. |
Beta Was this translation helpful? Give feedback.
-
|
When I reply using e-mail from Blackberry Hub on Blackberry 10, it adds some trailing JSON data at the end for me. |
Beta Was this translation helpful? Give feedback.
-
|
The reply by email functionality should also detect the standard email signature separator “-- ” and truncate the text that comes after it. That would be an easy way to also exclude the entire email thread from the Github comment, where a signature with the standard separator is present. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Feature Area
Issues
Body
I tried using the "Reply this email directly" feature for an issue thread for the first time last night
I decided to go to the website just to check if/how it went through, and was disappointed to discover that it included all of the usual "On [date], [email] wrote:" content of the reply. Worse still, despite there being new lines between my message and the reply content, GitHub seemingly deleted all of this, leading to the "somethingOn" at the end of my actual message
Not sure if this behavior is intentional or not, but most "reply via email" systems (and all of the ones I have used) have detected and deleted this reply history content.
Additionaly, when I went to fix this on the web, I discovered that I am not able to use/enable markdown for the edit, even though I'm now on the web.
Personally, I think markdown should be allowed via email, but if that's not desired, I should at least be able to enable it if I go to edit from the web.
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions