try out merge queues

[geekosaur]

Also enabling parallel checks, which should speed things up even more especially since Mergify forced us to separate the normal and squash-merge queues.

Also adjust the labels set for the bot to try to avoid making noise when it's being shoved straight in.

---

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

• [x] Patches conform to the coding conventions.
• [ ] ~~Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).~~ Mergify configuration is only read on master

[geekosaur]

BTW if this works then the next thing to try is to see if things we had to use merge+no rebase with work with merge me or squash+merge me. I think (per @TeofilC on Matrix) that Mergify cherry-picks commits into the queue PR, squashes them if it's the squash+merge queue, and rebases the result — which will be happening on Mergify's own local PR, not the one it's not allowed to rebase.

[ulysses4ever]

@geekosaur this sounds terrific, thank you for researching it! and thanks to @TeofilC for pitching in!

[mergify[bot]]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated.

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again. If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[geekosaur]

If we're lucky, this might even fix the above problem.

[ulysses4ever]

Yes. Fingers crossed...