[Bug] Route the category-remote-backend E2E through a real gateway route - #3544

✅ Rule: queue approved pull requests (queue)

• #approved-reviews-by >= 2
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• base = main
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = @mergify/Configuration changed
  • check-success = @mergify/Configuration has been deleted
• any of: [📌 queue requirement]
  • check-neutral = @mergify/Mergify Merge Protections
  • check-skipped = @mergify/Mergify Merge Protections
  • check-success = @mergify/Mergify Merge Protections
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue rule default]
    • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
    • base = main
    • github-review-approved [🛡 GitHub branch protection]
    • any of:
      • check-success = PR Gate
      • check-skipped = PR Gate
    • any of: [🛡 GitHub branch protection]
      • check-success = PR Gate
      • check-neutral = PR Gate
      • check-skipped = PR Gate

---

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

---

Mergify commands and options

More conditions and actions can be found in the documentation.

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

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

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