Fix tracking pickling, add worker error reporting #109
+52
−35
Mergify / Summary
succeeded
Oct 23, 2025 in 0s
2 rules match and 3 potential rules
✅ Rule: Label explore PRs (label)
-
files~=^explore/
✅ Rule: Label navigate PRs (label)
-
files~=^navigate/
Rule: Label observe PRs (label)
-
files~=^observe/
Rule: Label schemas PRs (label)
-
files~=^schemas/
Rule: Label ui PRs (label)
-
files~=^ui/
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
1 not applicable rule
Rule: merge scala-steward's PRs (merge)
-
-closed[📌 merge requirement] -
author=lucuma-steward[bot] - any of:
-
body~=labels:.*early-semver-minor -
body~=labels:.*early-semver-patch -
title=flake.lock: Update
-
-
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] -
status-success=Test (ubuntu-22.04, 3, temurin@17, rootJS) -
status-success=Test (ubuntu-22.04, 3, temurin@17, rootJVM) - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [🛡 GitHub branch protection]
-
check-success = Test (ubuntu-22.04, 3, temurin@17, rootJS) -
check-neutral = Test (ubuntu-22.04, 3, temurin@17, rootJS) -
check-skipped = Test (ubuntu-22.04, 3, temurin@17, rootJS)
-
- any of: [🛡 GitHub branch protection]
-
check-success = Test (ubuntu-22.04, 3, temurin@17, rootJVM) -
check-neutral = Test (ubuntu-22.04, 3, temurin@17, rootJVM) -
check-skipped = Test (ubuntu-22.04, 3, temurin@17, rootJVM)
-
- any of: [🛡 GitHub repository ruleset rule]
-
check-success = Test (ubuntu-22.04, 3, temurin@17, rootJS) -
check-neutral = Test (ubuntu-22.04, 3, temurin@17, rootJS) -
check-skipped = Test (ubuntu-22.04, 3, temurin@17, rootJS)
-
- any of: [🛡 GitHub repository ruleset rule]
-
check-success = Test (ubuntu-22.04, 3, temurin@17, rootJVM) -
check-neutral = Test (ubuntu-22.04, 3, temurin@17, rootJVM) -
check-skipped = Test (ubuntu-22.04, 3, temurin@17, rootJVM)
-
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