sigmavirus24/Todo.txt-python — Issue #9: GitHub integration for Issues/Pull Requests
Author: sigmavirus24
Created: 2011-12-18 18:02:03+00:00
State: open
Labels: Request For Comments

I was wondering if it would be worthwhile to fork the development and instead of managing a regular todo.txt list, if it would be useful for anyone if the todo.py script used the pull requests and issues on specified projects as the list of items todo. It would grab the issues/pull requests and one could sort by label, submitter, age, milestone, etc.

For example, if the script were to watch this project, it would look something like:
```6 Make GitPython Importing Conditional (sigmavirus24) @jvstein +Enhancement #{0.2 - No due date}
8 Testing and Performance Suite (sigmavirus24) @sigmavirus24 +Enhancement #{0.2 - No due date}
9 GitHub integration for Issues/Pull Requests (sigmavirus24) +Request_for_Comments #{Future - No due date}
```
The submitter name in parentheses doesn't exactly match the idea of a priority, but to whom it is assigned would make sense for the context tag (@) as well as using the project tag for the label(s) and the #{date} notation for the milestone.

I'm just curious if this is worth it. I would hope that interacting with the GitHub API wouldn't add too much heft. We could also remove all the GitPython dependencies.

Also for consideration:
* Allowing for the creation of issues from the script
* Allowing for someone to comment on issues
* Sorting by which issue has the most comments/etc.

I think these would add a bit too much, but that shouldn't be a reason not to do it.