We currently have all bugbug-related code inside our webhook event handler on webcompat.com. It would be great to separate it into a standalone Github app, so other repositories could reuse it.
The process consists of 3 steps:
1) Make a request to the bugbug http server for a prediction on a "issue opened" webhook event in the private repository.
2) If the issue is invalid, move the private issue to ml-autoclosed milestone.
3) Upon receiving milestoned webhook with ml-autoclosed - close the public issue and add a link to the private issue to the body, close the private issue.
As step 3 is pretty specific, likely only the first two steps should be handled by the new app.
Rough estimate: 1 week, and some time to figure out where to host the app.
We currently have all bugbug-related code inside our webhook event handler on webcompat.com. It would be great to separate it into a standalone Github app, so other repositories could reuse it.
The process consists of 3 steps: 1) Make a request to the bugbug http server for a prediction on a "issue opened" webhook event in the private repository. 2) If the issue is invalid, move the private issue to
ml-autoclosedmilestone. 3) Upon receivingmilestonedwebhook withml-autoclosed- close the public issue and add a link to the private issue to the body, close the private issue.As step 3 is pretty specific, likely only the first two steps should be handled by the new app. Rough estimate: 1 week, and some time to figure out where to host the app.