mergify: fix mergify config

[Nikhil-Ladha]

fix deprecated mergify config

[Nikhil-Ladha]

The mergify check fails for current config, but passes for the new config.
So, we should be good here.
Though, I am not sure if we need to manually merge the PR or so 🤔

[iPraveenParihar]

@Nikhil-Ladha do we have link to this config deprecation?

[iPraveenParihar]

The config LGTM.

Actually, I noticed there is a PR from Mergify to update the config - #712

Can you compare your PR with it?

[Nikhil-Ladha]

@Nikhil-Ladha do we have link to this config deprecation?

I couldn't find a link in the release docs or so, but the CI is failing with the details, as mentioned in my previous comment.

[Nikhil-Ladha]

Actually, I noticed there is a PR from Mergify to update the config - #712

Can you compare your PR with it?

It has a similar change for the 2 fields which this PR adds, so we are good wrt that.

[iPraveenParihar]

I think will need to merge it manually. @Rakshith-R PTAL

[nixpanic]

@Mergifyio queue

Not sure this works...

[nixpanic]

At least the new configuration is valid:

[mergify]

queue

🟠 Waiting for conditions to match

• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]