chore: land fix/session-recovery-freshness-20260820 - #768
Merged
Mergify / Summary
succeeded
Aug 29, 2026 in 2s
2 potential rules
Rule: automatic merge on CI success (merge)
-
-closed[📌 merge requirement] -
check-success=ci -
#approved-reviews-by>=1 -
#commits-behind = 0[🛡 GitHub branch protection] -
#review-threads-unresolved = 0[🛡 GitHub branch protection] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [📌 merge requirement]
-
check-neutral = Mergify Merge Protections -
check-skipped = Mergify Merge Protections -
check-success = Mergify Merge Protections
-
- any of: [🛡 GitHub branch protection]
-
check-success = pr-freshness -
check-neutral = pr-freshness -
check-skipped = pr-freshness
-
- any of: [🛡 GitHub branch protection]
-
check-success = lint -
check-neutral = lint -
check-skipped = lint
-
- any of: [🛡 GitHub branch protection]
-
check-success = test -
check-neutral = test -
check-skipped = test
-
Rule: automatic rebase (rebase)
-
-closed[📌 rebase requirement] -
conflict - any of:
-
#commits-behind > 0[📌 rebase requirement] -
-linear-history[📌 rebase requirement]
-
-
-conflict[📌 rebase requirement] -
queue-position = -1[📌 rebase requirement]
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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill 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
Loading