Skip to content
Small library to parse plain text email content
Ruby Shell
Branch: master
Clone or download

Latest commit

Latest commit f50d2dd Aug 7, 2019

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib bumping version Aug 7, 2019
script add script/release and script/test May 30, 2014
test Merge pull request #58 from olleolleolle/fix/add-link-to-description Jan 25, 2019
.gitignore
.travis.yml Add travis.yml Apr 10, 2019
LICENSE rakegemming it up Mar 7, 2011
README.md Update README.md Aug 27, 2018
Rakefile
email_reply_parser.gemspec Remove autogenerated notes from Gemspec, add description Nov 19, 2016

README.md

Email Reply Parser

EmailReplyParser is a small library to parse plain text email content. See the rocco-documented source code for specifics on how it works.

This is what GitHub uses to display comments that were created from email replies. This code is being open sourced in an effort to crowdsource the quality of our email representation.

See the Ruby docs for more information.

Usage

To parse reply body:

parsed_body = EmailReplyParser.parse_reply(email_body)

Problem?

If you have a question about the behavior and formatting of email replies on GitHub, check out support. If you have a specific issue regarding this library, then hit up the Issues.

Installation

Get it from GitHub or gem install email_reply_parser. Run rake to run the tests.

Contribute

If you'd like to hack on EmailReplyParser, start by forking the repo on GitHub:

https://github.com/github/email_reply_parser

The best way to get your changes merged back into core is as follows:

  • Clone down your fork
  • Create a thoughtfully named topic branch to contain your change
  • Hack away
  • Add tests and make sure everything still passes by running rake
  • If you are adding new functionality, document it in the README
  • Do not change the version number, I will do that on my end
  • If necessary, rebase your commits into logical chunks, without errors
  • Push the branch up to GitHub
  • Send a pull request to the github/email_reply_parser project.

Known Issues

Quoted Headers

Quoted headers aren't picked up if the email client breaks it up into multiple lines. GMail breaks up any lines over 80 characters for you.

On <date>, <author>
wrote:
> blah

Not to mention that we're searching for "on" and "wrote". It won't work with other languages.

Possible solution: Remove "reply@reply.github.com" lines...

Weird Signatures

Lines starting with - or _ sometimes mark the beginning of signatures:

Hello

--
Rick

Not everyone follows this convention:

Hello

Mr Rick Olson
Galactic President Superstar Mc Awesomeville
GitHub

**********************DISCLAIMER***********************************
* Note: blah blah blah                                            *
**********************DISCLAIMER***********************************
You can’t perform that action at this time.