Define recursive_*literal?
methods using macro
#298
Merged
Mergify / Summary
succeeded
Jun 20, 2024 in 0s
2 potential rules
Rule: automatic merge for master when reviewed and CI passes (merge)
-
-closed
[📌 merge requirement] -
label=auto-merge
-
status-success=Coverage | 2.6
-
status-success=Main Gem Specs | RuboCop: master | 2.6
-
status-success=Main Gem Specs | RuboCop: master | 3.1
-
status-success=Main Gem Specs | RuboCop: master | 3.2
-
status-success=Specs | 2.6
-
status-success=Specs | jruby-head
-
#changes-requested-reviews-by=0
-
#review-requested=0
-
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] -
base=master
-
status-success=Coding Style | 3.0
-
status-success=Main Gem Specs | RuboCop: master | 2.7
-
status-success=Main Gem Specs | RuboCop: master | 3.0
-
status-success=Specs "modern" | 3.0
-
status-success=Specs | 2.7
-
status-success=Specs | 3.0
-
status-success=Specs | 3.1
-
status-success=Specs | 3.2
-
status-success=Specs | head
-
status-success=Specs | truffleruby
-
status-success=Specs | truffleruby-head
- any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
Rule: delete head branch after auto-merge (delete_head_branch)
-
label=auto-merge
-
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!
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