A while back as subscriber to a shifty plan had to ask if they can keep their web hook automation configuration within their project. This would allow other developers on the team to modify this without having to sign into blairvilleshift.com.
At first I set on this while I did this request I set on it for a while. I typically do this for one off feature request. I like to wait until another user requested or I at least Feel the same need for it.
After working on some of my after working on some additional side projects in 2025 after working on more side projects in 2025, I finally realize the need.
The underlying issue is that the automation specified to run on web hooks is per subscription. Not per repository.
So this request was actually a two in one feature. Not only the convenience of having it in the project, repository visible by all developers. But also the fact that this would allow per project automation.
I could of course, put this in the UI, but the combination of benefits Seem to make more sense, putting it in the project.
So, you may now add a Shift.Yamo file to your project the top level of your Laville project. If this file is detected, it will override the it will supersede it will take priority over the default automation use, specifyfor your subscription within lavellshift.com. You have configured for your subscription.
The format of this file is exactly the same as the format of your workbench build. But having it within your project allows, you to share it more easily. Add additional comments and have all developers. Keep it up.