https://github.com/sorbits/github-email-api

Assign labels and close issues via email
https://github.com/sorbits/github-email-api

Last synced: 2 days ago
JSON representation

Assign labels and close issues via email

• Host: GitHub
• URL: https://github.com/sorbits/github-email-api
• Owner: sorbits
• Created: 2013-05-01T12:00:35.000Z (over 11 years ago)
• Default Branch: master
• Last Pushed: 2014-07-29T13:00:50.000Z (over 10 years ago)
• Last Synced: 2024-11-10T13:47:38.973Z (2 months ago)
• Language: Ruby
• Size: 185 KB
• Stars: 4
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# GitHub Email API

The GitHub email API script reads an email from standard in and will do one of two things:

1. If the email is from `[email protected]` then it will change the `Reply-To` header into `[email protected]` and write the result to standard out.

	This means replies are sent to yourself instead of GitHub which allow us to process them before they go to GitHub.

2. If the email is to `[email protected]` then it will look for lines in the email matching these patterns:

		/^state:\s*(open|closed)/

		/^assignee:\s*(.*)/

		/^title:\s*(.+)/

		/^labels?:\s*(.*)/

	If any are found then it will update the issue (found by looking at the `Message-ID` header) with the corresponding value.

	In addition to updating the issue, it will resend the email to the original reply-to address after having removed all command lines, assuming the (non-quoted) body of the email is non-empty.

## Install

1. Clone this repository to your server:

		git clone https://github.com/sorbits/github-email-api.git

2. Install required gems (via [bundler](http://gembundler.com/)):

		bundle install

3. [Create a GitHub OAuth token](https://help.github.com/articles/creating-an-oauth-token-for-command-line-use):

		curl -u «user» -d '{"scopes":["repo"],"note":"GitHub Email API"}' https://api.github.com/authorizations

4. Create `~/.config/github-email-api`, e.g.:

		oauth_token: «token»

		email:       "[email protected]"

		log_file:    "~/logs/github-email-api.log"

5. Setup your mail server to run email through [`procmail`](http://www.procmail.org/).

6. Add the following to `~/.procmailrc`:

		# Handle GitHub notification email

		:0fw

		* ^From:.*\

		| "/path/to/github-email-api"

	

		# Handle replies to a notification (me+…@example.org)

		:0w

		* ^To:.*\

		| "/path/to/github-email-api"

		# Send an email if the above command failed

		:0e

		| (formail -rtI'From: "GitHub Email API" ' \

		    ; echo "Error processing reply, see log for details.") \

		| /usr/sbin/sendmail -oi -t [email protected]

## Updating Labels

Label names can be prefixed with a minus (`-`) to remove them. For consistency an optional plus (`+`) prefix is allowed when setting labels. Example:

	label: bug

	label: +bug

	label: -bug

Multiple labels can be specified by separating them with a comma or using multiple `label`/`labels` lines.

	labels: -too-vague, +crash

If you use a label name that doesn’t already exist, it will be created.

## Problems

* The `github-email-api` script will not retry incase of errors, e.g. if `api.github.com` return a `500 Internal Server Error`.

* Issues closed via email generally show “you closed this issue…” before the reply (presumably stating the reason) since the reply is added via (GitHub’s own) email API which has a noticeable delay.

* Setting up the GitHub email API is probably too complex for most users.