The path I was going was to use @rvagg's github-webhook-handler which sets things up in an evented way: when hook data comes in, emit the event. I took it a step further to emit event+'.'+action for more granularity.
I created a scripts directory where scripts could be added and they can listen to whatever events they need.
Here is echo.js that I created as an example:
vargithub=require('../github.js');module.exports=function(org){org.on('issue_comment.created',event=>{//this would be circular if we don't ignore ourself!if(!event.sender||!github.me||event.sender.id===github.me.id)return;varrepo=event.repository;github.issues.createComment({user: repo.owner.login,repo: repo.name,number: event.issue.number,body: event.comment.body})});};How do you feel about going this route? It looks like the work in pollTravis could be done with this approach.
But, that was just my approach... ;) What way(s) do you see extending this to include other scripts/workers?
The path I was going was to use @rvagg's github-webhook-handler which sets things up in an evented way: when hook data comes in, emit the event. I took it a step further to emit
event+'.'+actionfor more granularity.I created a scripts directory where scripts could be added and they can listen to whatever events they need.
Here is echo.js that I created as an example:
How do you feel about going this route? It looks like the work in
pollTraviscould be done with this approach.But, that was just my approach... ;) What way(s) do you see extending this to include other scripts/workers?