Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Find a way to get github to send email notifications to the laser team #900
I've created a Github team @DoESLiverpool/laser-maintenance. I had wondered if we could then assign issues to it, in order for the team to receive notifications, but that doesn't seem to be the case :-(
So, I think that means we'll need to roll our own. Or look to see if anyone else has built something to solve the problem...
OK well that seems to work quite well. The major problem is that as a "casual developer" I am apparently no longer allowed to Tweet without jumping through burning hoops of fire.
Anyhoo biting my tongue for the moment...
GitHub Webbooks allow us to propagate events which include events relating to issue creation / label addition and so forth. @see https://developer.github.com/v3/activity/events/types/#issuesevent (@zarino)
(As much as I hate myself for admitting it the whole JS <-> JSON thing is awesome. So much boring work involves parsing. I love how easy it is to map data to object properties although I'm still not entirely convinced that it's at all robust)
So there's a test repo here: https://github.com/DoESLiverpool/a-test-repo
I've put a couple of test issues in there and a label "email-the-directors"
You can add and remove the email and firstname.lastname@example.org will be emailed with what's occurring wrt the issue and the label.
Flow looks like this
If the DMZ / sandboxed area in #932 were looked at we might put a public facing Node-Red DoES infrastructure VPS in place to handle this kind of thing?
I think it'd be better to comment on the issue rather than send an email, in this case - because...
And then we'll need to set up the publicly accessible NodeRED instance. I wonder if sticking it on the VPS running https://organisers.doesliverpool.com would work, as it's a pretty easy install with Docker (which that's using to run FabManager)?
For a completely different approach (which I only learnt about a day or so ago), you could set up a Github Action, which seems to be a way to get Github to run a script when certain events happen (including adding a label). There's a walkthrough of it at [https://blog.jessfraz.com/post/the-life-of-a-github-action/], which I've not finished reading yet :-)