Normalization of GitVersionTargetFramework and fallback scenario #4206
Mergify / Summary
succeeded
Oct 31, 2024 in 1s
1 rule matches
✅ Rule: Thank contributor (comment)
-
-author~=^dependabot(|-preview)\[bot\]$ -
merged
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
2 not applicable rules
Rule: Automatic approve on dependabot PR (review)
-
author~=^dependabot(|-preview)\[bot\]$
Rule: Automatic merge on dependabot PR after success CI (merge)
-
-closed[📌 merge requirement] -
author~=^dependabot(|-preview)\[bot\]$ -
#approved-reviews-by >= 1[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0[🛡 GitHub branch protection] -
#commits-behind=0 -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] -
check-success=DotNet Format -
check-success=Release -
repository-full-name=GitTools/GitVersion - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [🛡 GitHub branch protection]
-
check-success = CodeQL -
check-neutral = CodeQL -
check-skipped = CodeQL
-
- any of: [🛡 GitHub branch protection]
-
check-success = Build & Package / windows-latest -
check-neutral = Build & Package / windows-latest -
check-skipped = Build & Package / windows-latest
-
- any of: [🛡 GitHub branch protection]
-
check-success = Build & Package / ubuntu-latest -
check-neutral = Build & Package / ubuntu-latest -
check-skipped = Build & Package / ubuntu-latest
-
- any of: [🛡 GitHub branch protection]
-
check-success = DotNet Format -
check-neutral = DotNet Format -
check-skipped = DotNet Format
-
- any of: [🛡 GitHub branch protection]
-
check-success = Test / ubuntu-latest - net6.0 -
check-neutral = Test / ubuntu-latest - net6.0 -
check-skipped = Test / ubuntu-latest - net6.0
-
- any of: [🛡 GitHub branch protection]
-
check-success = Test / windows-latest - net6.0 -
check-neutral = Test / windows-latest - net6.0 -
check-skipped = Test / windows-latest - net6.0
-
- any of: [🛡 GitHub branch protection]
-
check-success = Test / ubuntu-latest - net8.0 -
check-neutral = Test / ubuntu-latest - net8.0 -
check-skipped = Test / ubuntu-latest - net8.0
-
- any of: [🛡 GitHub branch protection]
-
check-success = Test / windows-latest - net8.0 -
check-neutral = Test / windows-latest - net8.0 -
check-skipped = Test / windows-latest - net8.0
-
- any of: [🛡 GitHub branch protection]
-
check-success = Release -
check-neutral = Release -
check-skipped = Release
-
- any of: [🛡 GitHub branch protection]
-
check-success = Test / macos-15 - net6.0 -
check-neutral = Test / macos-15 - net6.0 -
check-skipped = Test / macos-15 - net6.0
-
- any of: [🛡 GitHub branch protection]
-
check-success = Test / macos-15 - net8.0 -
check-neutral = Test / macos-15 - net8.0 -
check-skipped = Test / macos-15 - net8.0
-
- any of: [🛡 GitHub branch protection]
-
check-success = Build & Package / macos-15 -
check-neutral = Build & Package / macos-15 -
check-skipped = Build & Package / macos-15
-
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