Billy Keyes

I agree the existing default behavior of substring matching was probably a mistake, but I'm not sure we want to change the behavior of the app at this point given...

As of 1.40.0, it's now possible to override the default approval methods in the server. Internally, we're using the following defaults: ```yaml approval_defaults: options: methods: comments: [] comment_patterns: - "^\\s*:\\+1:\\s*$"...

At the moment, there is no support for combining rules from different locations in to a single policy. You can find some requests for similar features in #906 and #319....

The add-in generates the names for the export by combining (with a forward slash) all of the names on the path from the selected component(s) to the the actual bodies....

There's currently no support for ignoring approvals from specific users who otherwise meet the conditions specified in the rule. I think your best option will be to create a new...

This sounds similar to #184 and is something that has also come up in our internal discussions. Part of the challenge is designing a flexible way to write the relevant...

While I'm not opposed to making this configurable, could you share more details about the failures you're seeing in large organizations that would be fixed by more retries? There may...

Most existing tools we've tried (like Dependabot and our internal Excavator tooling) don't handle major version updates for Go modules particularly well and so don't do a great job at...

Thanks to @yevbar, PRs for these upgrades should be automated going forward (although we'll still need to manually approve and release them.)