Use drupal.org API to sync issue queues #28
Description
This is a feature request.
Problem/Motivation
Hubdrop currently syncs VCS from drupal.org to github. This is an interesting feature, but issue queues remain exclusively on one or the other. When someone files an issue on drupal.org, the github issue queue is not updated.
Proposed solution
- When an issue is posted on a drupal.org project page, use the Drupal.org API to copy that issue into the github issue queue.
- When an issue is posted on github (not possible at the moment, if I'm understanding this right) copy that issue to the drupal.org issue queue. Use the github API to add some comment like "comments on this issue will appear automatically at drupal.org/123"
- When a pull request is created, users should put the drupal.org issue number in the subject. Hubdrop should use this value to post the pull request contents as a patch in the appropriate issue queue.
Advantages
- Cross posting patches onto drupal.org ensures that the testbot will be used to test pull requests
- Capturing drupal.org issue queues on github gives essential context to github pull requests.
- Capturing drupal.org issue queues on github makes it possible to evaluate permenant migration to github, because a large portion of drupal.org data will already be migrated to github.