| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
We no longer forward GitHub notifications to the mailing list.
|
|
Email::MIME sometimes prepends an empty line when returning an email as
string :-/
|
|
This shouldn't happen in practice[tm], but if we receive the header
line "Subject: [monitoring-plugins] ", then we won't touch it anymore.
|
|
When wrapping a line that begins with a ">", let all resulting lines
begin with a ">". (Properly handle nested blockquotes, too.)
|
|
Don't wrap long lines in a code block.
|
|
Now that we edit the GitHub notifications anyway, lets also strip the
[monitoring-plugins] tag. We don't strip the tags of our other
repositories, so that notifications for them do stand out (on the rare
occasion we receive them).
|
|
Wrap individual lines instead of formatting whole paragraphs, so that
lists such as
* first item
* second item
aren't rewrapped.
|
|
Also catch the case where an issue was closed in a commit message, e.g.:
| Closed #123 via c5dc81cd28a9491115b4d13b959b0fc8e2df9a6c.
|
|
Have GitHub send notifications to plugins+github@, and try to
distinguish actual user comments from mere status change reports. Right
now, both types of notifications are forwarded to the devel@ list, but
in the future, we could choose to omit the status change emails.
While at it, the messages are also modified to make them more suitable
for being forwarded to a mailing list.
|
