merge queue: embarking main (4d85c14), #2349, #2350 and #2351 together

[mergify]

🎉 This pull request has been checked successfully and will be merged. 🎉

Branch main (4d85c14), #2349, #2350 and #2351 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #2351.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

• schedule=Mon-Fri 09:00-17:30[Europe/Paris]
• all of:
  • check-success=docs
  • check-success=lint

Required conditions to stay in the queue:

• #approved-reviews-by>=2
  • docs(integrations): fix Jenkins link #2351
• #changes-requested-reviews-by=0
  • docs(integrations): fix Jenkins link #2351
• #review-requested=0
  • docs(integrations): fix Jenkins link #2351
• #review-threads-unresolved=0
  • docs(integrations): fix Jenkins link #2351
• check-success=semantic-pull-request
  • docs(integrations): fix Jenkins link #2351
• label!=manual merge
  • docs(integrations): fix Jenkins link #2351
• all of:
  • check-success=docs
    • docs(integrations): fix Jenkins link #2351
  • check-success=lint
    • docs(integrations): fix Jenkins link #2351

Visit the Mergify Dashboard to check the state of the queue default.

---

More information about Mergify merge queue can be found in the documentation.

Mergify commands

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the queue rules

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

---
pull_requests:
  - number: 2351
...