fix: Add missing lock around files dictionary #1260
Merged
This check has been archived and is scheduled for deletion.
Learn more about checks retention
Mergify / Summary
succeeded
Apr 8, 2025 in 0s
1 potential rule
Rule: Automatic merge on approval (merge)
-
#approved-reviews-by>=1 -
-closed[📌 merge requirement] -
#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: [🛡 GitHub branch protection]
-
check-success = Unit tests (macos-latest) -
check-neutral = Unit tests (macos-latest) -
check-skipped = Unit tests (macos-latest)
-
- any of: [🛡 GitHub branch protection]
-
check-success = Unit tests (windows-latest) -
check-neutral = Unit tests (windows-latest) -
check-skipped = Unit tests (windows-latest)
-
- any of: [🛡 GitHub branch protection]
-
check-success = Unit tests (ubuntu-latest) -
check-neutral = Unit tests (ubuntu-latest) -
check-skipped = Unit tests (ubuntu-latest)
-
- any of: [🛡 GitHub branch protection]
-
check-success = Testably/Conventional-Commits -
check-neutral = Testably/Conventional-Commits -
check-skipped = Testably/Conventional-Commits
-
- any of: [🛡 GitHub branch protection]
-
check-success = API tests -
check-neutral = API tests -
check-skipped = API tests
-
💖 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: Automatic merge for Renovate pull requests (merge)
-
-closed[📌 merge requirement] -
author=renovate[bot] -
#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: [🛡 GitHub branch protection]
-
check-success = Unit tests (macos-latest) -
check-neutral = Unit tests (macos-latest) -
check-skipped = Unit tests (macos-latest)
-
- any of: [🛡 GitHub branch protection]
-
check-success = Unit tests (windows-latest) -
check-neutral = Unit tests (windows-latest) -
check-skipped = Unit tests (windows-latest)
-
- any of: [🛡 GitHub branch protection]
-
check-success = Unit tests (ubuntu-latest) -
check-neutral = Unit tests (ubuntu-latest) -
check-skipped = Unit tests (ubuntu-latest)
-
- any of: [🛡 GitHub branch protection]
-
check-success = Testably/Conventional-Commits -
check-neutral = Testably/Conventional-Commits -
check-skipped = Testably/Conventional-Commits
-
- any of: [🛡 GitHub branch protection]
-
check-success = API tests -
check-neutral = API tests -
check-skipped = API tests
-
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