Bors currently "Caches" PR approvals and only updates that cache when a new review is submitted. This can be a problem when different branch protections are put in place enforcing more reviewers or CODEOWNERS causing Bors to still attempt to land a PR that was approved by an old config but not be the new one.
Bors currently "Caches" PR approvals and only updates that cache when a new review is submitted. This can be a problem when different branch protections are put in place enforcing more reviewers or CODEOWNERS causing Bors to still attempt to land a PR that was approved by an old config but not be the new one.