Using json-e will make it a lot easier to produce exactly the desired task in .taskcluster.yml, without relying on data-munging by taskcluster-github. Basically, we can make the whole webhook payload available to json-e, and the user can access whatever fields they would like. We'll need some kind of gentle transition from the current templating schem -- maybe we just go from version 1 to version 2?

You have a link to "json-e"? Thank you!

One feature that will be important here is a way to reduce redundancy -- .taskcluster.yml files tend to repeat the same task boilerplate over and over, and users will want to be able to write that once and then generate lots of tasks. I don't know what that would look like, but we can talk about ideas.

I've started twiddling around with this, after https://github.com/taskcluster/mozilla-taskcluster/pull/116

This was deployed on Friday.

oh, right, this is tc-github.

I think this is done, right Irene? A two-year-old-bug!

Yep, this is done!