Moved TriggerType enum to dedicated file to avoid repetition in hardware component classes #1962
Mergify / Summary
succeeded
Dec 20, 2024 in 0s
3 potential rules
Rule: Backport to humble at reviewers discretion (backport)
-
label=backport-humble -
base=master -
merged[📌 backport requirement]
Rule: Backport to iron at reviewers discretion (backport)
-
label=backport-iron -
base=master -
merged[📌 backport requirement]
Rule: Ask to resolve conflict (comment)
-
conflict -
author!=dependabot[bot] -
author!=mergify[bot]
💖 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: Ask to resolve conflict for backports (comment)
-
author=mergify[bot] -
conflict
Rule: development targets master branch (comment)
-
base!=master -
author!=bmagyar -
author!=christophfroehlich -
author!=dependabot[bot] -
author!=destogl -
author!=mergify[bot] -
author!=saikishor
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