A while back a subscriber to a Shifty Plan asked if they could keep their webhook automation configuration within their project. This would allow other developers on the team to modify this without having to sign into Shift.
At first, I sat on this for a while. I typically do this for one-off feature requests. I like to wait until another user requests it, or I feel the need myself. After working on my own side projects, I finally realized the need.
The underlying issue is that the automation specified to run on webhook is per subscription. Not per project. So this request was actually a two in one feature. It provided the convenience of having this configuration in the repository, visible by all developers. And also allowed project-specific automation.
I could have updated the UI, but I really liked putting this in the repository. Many other tools do this. And, it's actually a lot less work. Probably less than 20 lines of code, as opposed to new views, controllers, database columns, and still the same 20 lines of code.
Underneath, the webhook automation is really just YAML. The same YAML you write when using the Shift Workbench. So now, you may add a shift.yaml file to the top-level of your Laravel project. If this file is detected, it takes priority over the default automation configured for your subscription.