coverage: avoid skipping brittle tests in FileSystemWatcher
#521
Mergify / Summary
succeeded
Mar 29, 2024 in 1s
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=Test (.NET Framework)
-
check-neutral=Test (.NET Framework)
-
check-skipped=Test (.NET Framework)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Test (Examples)
-
check-neutral=Test (Examples)
-
check-skipped=Test (Examples)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Test (MacOS)
-
check-neutral=Test (MacOS)
-
check-skipped=Test (MacOS)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Test (Windows)
-
check-neutral=Test (Windows)
-
check-skipped=Test (Windows)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Test (Ubuntu)
-
check-neutral=Test (Ubuntu)
-
check-skipped=Test (Ubuntu)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Codacy Static Code Analysis
-
check-neutral=Codacy Static Code Analysis
-
check-skipped=Codacy Static Code Analysis
-
- any of: [🛡 GitHub branch protection]
-
check-success=SonarCloud Code Analysis
-
check-neutral=SonarCloud Code Analysis
-
check-skipped=SonarCloud Code Analysis
-
💖 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=Test (.NET Framework)
-
check-neutral=Test (.NET Framework)
-
check-skipped=Test (.NET Framework)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Test (Examples)
-
check-neutral=Test (Examples)
-
check-skipped=Test (Examples)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Test (MacOS)
-
check-neutral=Test (MacOS)
-
check-skipped=Test (MacOS)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Test (Windows)
-
check-neutral=Test (Windows)
-
check-skipped=Test (Windows)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Test (Ubuntu)
-
check-neutral=Test (Ubuntu)
-
check-skipped=Test (Ubuntu)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Codacy Static Code Analysis
-
check-neutral=Codacy Static Code Analysis
-
check-skipped=Codacy Static Code Analysis
-
- any of: [🛡 GitHub branch protection]
-
check-success=SonarCloud Code Analysis
-
check-neutral=SonarCloud Code Analysis
-
check-skipped=SonarCloud Code Analysis
-
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
Loading