>> And the devs honestly try to do their best to remember to configure the >> filters, but for some reason they disappear for them, don't ask me why, >> I don't know. This is an open source project team, not a work place. > > This sounds like it could be easily solved by continuous integration. > You could set up a job on any of a variety of services that checks that > a pull request or other commit is clean when when the filter runs. If > it doesn't pass, the code doesn't merge. This is an excellent idea wrt to PRs. Thank you, Brian! I will implement that. It doesn't help with direct commits to master, since CI would be detecting it after it was committed. And when that happens we all know that already because 'git pull' fails. -- ________________________________________________ Stas Bekman <'))))>< <'))))>< https://stasosphere.com https://chestofbooks.com https://experientialsexlab.com https://stason.org https://stasosphere.com/experience-life/my-books
