[VVP-4769] Show installation token after Community Edition installation #99
Mergify / Summary
succeeded
Jan 20, 2025 in 3s
15 potential rules
The configuration uses the deprecated
merge_method
attribute of the queue action in one or morepull_request_rules
. It must now be used under thequeue_rules
configuration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
Rule: Auto-Merge on Label (queue)
-
#approved-reviews-by>=1
-
label=ready-to-merge
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by >= 1
[🛡 GitHub branch protection] -
#approved-reviews-by >= 1
[🛡 GitHub repository ruleset rule] -
branch-protection-review-decision = APPROVED
[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0
[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0
[🛡 GitHub repository ruleset rule]
-
- all of: [📌 queue conditions of queue
-
-closed
[📌 queue requirement] -
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
Rule: backport 2.14 (backport)
-
label=release-2.14
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.13 (backport)
-
label=release-2.13
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.12 (backport)
-
label=release-2.12
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.11 (backport)
-
label=release-2.11
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.10 (backport)
-
label=release-2.10
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.9 (backport)
-
label=release-2.9
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.8 (backport)
-
label=release-2.8
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.7 (backport)
-
label=release-2.7
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.6 (backport)
-
label=release-2.6
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.5 (backport)
-
label=release-2.5
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.4 (backport)
-
label=release-2.4
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.3 (backport)
-
label=release-2.3
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.2 (backport)
-
label=release-2.2
-
merged
-
merged
[📌 backport requirement]
Rule: backport 2.1 (backport)
-
label=release-2.1
-
merged
-
merged
[📌 backport requirement]
1 not applicable rule
Rule: Auto-Merge Green Backports (queue)
-
head~=mergify/bp
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by >= 1
[🛡 GitHub branch protection] -
#approved-reviews-by >= 1
[🛡 GitHub repository ruleset rule] -
branch-protection-review-decision = APPROVED
[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0
[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0
[🛡 GitHub repository ruleset rule]
-
- all of: [📌 queue conditions of queue
-
-closed
[📌 queue requirement] -
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] -
label!=conflicts
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
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