Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ci: removed deprecated fields in mergify (#9825)
closes: #9836 ## Description This PR removes the following deprecated fields in the queue action in mergify: - `merge_method` - `update_method` Mergify recommends using these fields in the `queue_rules` section instead. each queue can only have a single update/merge method, so In order to have different update/merge methods for different pull_requests we must create multiple queues This creates two issues in priority: - Each queue has its own priority level i.e. queues defined first are executed first. This creates a difference in priority that we do no intend. - since we have to create multiple queues our previous method of creating a high priority queue will not work, instead we'll have to duplicate the queues again, creating one queue for high_priority and one for normal priority. As of now there exists no way around these problems. After some discussion with the Mergify team this is what they recommend: > We’re WIP in removing the priorities between queues, but in the meantime you can mitigate this with `allow_checks_interruption` set to false and `disallow_checks_interruption_from_queues` ### Testing of PR: I tested this PR to verify that all queues work as expected. these 3 PRs were created for this purpose: frazarshad/mergify-experiements#20 frazarshad/mergify-experiements#21 frazarshad/mergify-experiements#22 ![image](https://github.com/user-attachments/assets/145c2e6b-a97b-4c0a-bcfb-912eb9916482) The new priority_rules were also checked and work as expected: ![Screenshot 2024-08-05 at 4 33 22 PM](https://github.com/user-attachments/assets/f49bcdce-5fcf-44cd-b117-074952fdc38a) ### Security Considerations ### Scaling Considerations ### Documentation Considerations ### Testing Considerations ### Upgrade Considerations
- Loading branch information