Triggered runs (events from Slack or GitHub) #75
Replies: 1 comment
|
Hey @brynary just bumping this one - I was going to post it on Discord then I remembered you have this here. tl;dr: it would be fantastic if Fabro could start/resume workflows based on events from GH (e.g. review/comment/approval) and other sources too (e.g. deployment pipelines).
I forgot a workflow running overnight and came back to Fabro consuming GBs of memory, the UI was barely usable anymore with so many stages. But that's my fault, I'm forcing a feature that is not built yet (I have it running in a loop with scripts checking for PR changes). But it's the best way I've found so far. I want to use Fabro for some personal tooling as well, but without this feature I would have to build a whole software around it and I'd prefer to just help you build it on Fabro. Do you already have an idea of how you want this to be built, or is this something you'd like to have a plan put together first? |

Uh oh!
There was an error while loading. Please reload this page.
Support triggering workflow runs in response to external events such as GitHub webhooks (push, PR opened, issue created, comment) or Slack messages. This would enable reactive workflows that respond automatically to repository or team activity.
All reactions