Use a .deployignore file rather than setting in actions

I’ve used another service that uses a .deployignore file that gets placed in the root of the repo and makes it much easier to manage files to include/exclude. This is especially useful for updating multiple projects at a time like those that all use the same configuration (E.g. WordPress sites). It’d be great if Buddy could implement something similar as I think it’d make it easier to manage and a be a good timesaver.

Hi!

We have such a feature in our backlog and we have just raised its priority. Unfortunately, I am unable to provide you with any solid ETA at the moment but be sure to check our blog every Thursday for release notes.