Bump tw-elements from 1.1.0 to 2.0.0 #5899
Open
Mergify / Summary
succeeded
Jul 11, 2024 in 4s
2 potential rules
Rule: automatic merge for master when reviewed and CI passes (queue)
-
label=ready-to-merge
-
-draft
[📌 queue requirement] - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by>=1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success=build
-
check-neutral=build
-
check-skipped=build
-
- any of: [🛡 GitHub branch protection]
-
check-success=SonarCloud Code Analysis
-
check-neutral=SonarCloud Code Analysis
-
check-skipped=SonarCloud Code Analysis
-
-
- all of: [📌 queue conditions of queue
Rule: delete head branch after merge (delete_head_branch)
-
closed
[📌 delete_head_branch requirement] -
merged
💖 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: ask developers to resolve conflict (comment)
-
-author~=^dependabot(|-preview)\[bot\]$
-
conflict
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