While this is still in the conceptual phase, I’ll continue to keep brainstorming on it 
Regarding conditions, I’ve been wondering how much flexibility could actually be built in. It would be great to implement something like the screenshot, where the user has full control over how criteria are constructed. Allowing users to select data from the trigger_context, define how it’s evaluated, and set what it’s evaluated against - while also letting them choose between AND / OR logic.
It would unlock more complex scenarios, whilst also keeping it easy and intuitive to understand like:
if {{category}} is one of {{user selected value}}ANDif {{tag}} is not {{user selected value}}
The screenshot also includes what to do after the condition check, but this would probably only apply for branched pipelines - for a linear pipeline, which covers most cases, then it would probably simply end
