Use &mut self in NotificationProcessor::init
#3
Mergify / Summary
succeeded
Apr 25, 2024 in 0s
3 rules match and 5 potential rules
Rule: automerge if approved and tests pass (queue)
-
-closed -
label=automerge -
#approved-reviews-by>=1 -
-conflict -
-draft -
-draft[📌 queue requirement] -
-label=nomerge -
base~=main - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of [📌 queue conditions of queue
default]
- all of [📌 queue conditions of queue
✅ Rule: cleanup post-merge (delete_head_branch)
-
closed[📌 delete_head_branch requirement] -
merged
✅ Rule: cleanup post-merge (label)
-
merged
Rule: notify on merge (comment)
-
label=automerge -
merged
Rule: alert on merge conflict (comment)
-
conflict -
label=automerge
Rule: alert on tests failure for automerge (comment)
-
label=automerge -
status-failure=commit
Rule: auto-assign author (assign)
-
#assignee=0
✅ Rule: feature label (label)
-
head~=(?i)^feat(ure)?
7 not applicable rules
Rule: fix label (label)
-
head~=(?i)^(bug|hot)?fix
Rule: chore label (label)
-
head~=(?i)^chore
Rule: docs label (label)
-
head~=(?i)^doc
Rule: release (label)
-
head~=(?i)^rel(ease)?
Rule: spike (label)
-
head~=(?i)^spike
Rule: rename (label)
-
head~=(?i)^rename
Rule: style (label)
-
head~=(?i)^style
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