Skip to content

Address review feedback in concurrent config update test

27512e9
Select commit
Loading
Failed to load commit list.
Merged

Use writeFileAtomic in Distribution.Client.Config and remove .tmp workaround #28

Address review feedback in concurrent config update test
27512e9
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Apr 24, 2026 in 2s

7 potential rules

⚠️ The pull request has been merged by @ulysses4ever

Rule: Wait for 2 days before validating merge (label)

  • #approved-reviews-by>=2
  • any of:
    • label=merge me
    • label=merge+no rebase
    • label=squash+merge me
  • any of:
    • updated-at<2 days ago
    • label=priority: high :fire:

Rule: Waiting out merge delay (used by bot) (label)

  • #approved-reviews-by>=2
  • -closed
  • check-success=Bootstrap post job
  • check-success=Doctest Cabal
  • check-success=Meta checks
  • check-success=Validate post job
  • check-success=docs/readthedocs.org:cabal
  • check-success=fourmolu
  • check-success=hlint
  • any of:
    • label=merge me
    • label=merge+no rebase
    • label=squash+merge me
  • #changes-requested-reviews-by=0
  • -draft
  • -label=merge delay passed
  • -label=priority: high :fire:
  • base=master

Rule: Mergify hasn't merged a PR yet (label)

  • #approved-reviews-by>=2
  • -closed
  • -merged
  • check-success=Bootstrap post job
  • check-success=Doctest Cabal
  • check-success=Meta checks
  • check-success=Validate post job
  • check-success=docs/readthedocs.org:cabal
  • check-success=fourmolu
  • check-success=hlint
  • label=merge delay passed
  • #changes-requested-reviews-by=0
  • -draft
  • base=master
  • updated-at<3 days ago

Rule: Put pull requests in the rebase+merge queue (queue)

  • #approved-reviews-by>=2
  • -closed [📌 queue requirement]
  • label=merge delay passed
  • label=merge me
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=^blocked:
  • base=master
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue rule default]

Rule: Put pull requests in the squash+merge queue (queue)

  • #approved-reviews-by>=2
  • -closed [📌 queue requirement]
  • label=merge delay passed
  • label=squash+merge me
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=^blocked:
  • base=master
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue rule squash-merge]

Rule: Merge "merge+no rebase" pull requests directly (without a queue) (merge)

  • #approved-reviews-by>=2
  • -closed [📌 merge requirement]
  • label=merge delay passed
  • label=merge+no rebase
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • -label~=^blocked:
  • base=master
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Label backports as such (label)

  • body~=automatic backport

4 not applicable rules

Rule: Put release branch pull requests in the rebase+merge queue (queue)

  • #approved-reviews-by>=2
  • -closed [📌 queue requirement]
  • base!=master
  • label=merge me
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label=backport
  • -label~=^blocked:
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue rule default]

Rule: Put release branch pull requests in the squash+merge queue (queue)

  • #approved-reviews-by>=2
  • -closed [📌 queue requirement]
  • base!=master
  • label=squash+merge me
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label=backport
  • -label~=^blocked:
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue rule squash-merge]

Rule: Put backports in the rebase+merge queue (queue)

  • #approved-reviews-by>=1
  • -closed [📌 queue requirement]
  • base!=master
  • label=backport
  • label=merge me
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=^blocked:
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue rule default]

Rule: Put backports in the squash+merge queue (queue)

  • #approved-reviews-by>=1
  • -closed [📌 queue requirement]
  • base!=master
  • label=backport
  • label=squash+merge me
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=^blocked:
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue rule squash-merge]
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