fix(ux): add Ordered Qty
column in Get Items From > MR
#36486
Merged
This check has been archived and is scheduled for deletion.
Learn more about checks retention
Mergify / Summary
succeeded
Feb 10, 2024 in 2s
1 rule matches and 5 potential rules
Rule: backport to develop (backport)
-
label="backport develop"
-
merged
[📌 backport requirement]
✅ Rule: backport to version-14-hotfix (backport)
-
label="backport version-14-hotfix"
-
merged
[📌 backport requirement]
Rule: backport to version-15-hotfix (backport)
-
label="backport version-15-hotfix"
-
merged
[📌 backport requirement]
Rule: backport to version-13-hotfix (backport)
-
label="backport version-13-hotfix"
-
merged
[📌 backport requirement]
Rule: Automatic merge on CI success and review (merge)
-
#approved-reviews-by>=1
-
-closed
[📌 merge requirement] -
status-success=Patch Test
-
status-success=Python Unit Tests (1)
-
status-success=Python Unit Tests (2)
-
status-success=Python Unit Tests (3)
-
status-success=Semantic Pull Request
-
status-success=Sider
- any of: [🛡 GitHub branch protection]
-
check-neutral=Patch Test
-
check-skipped=Patch Test
-
check-success=Patch Test
-
- any of: [🛡 GitHub branch protection]
-
check-neutral=Python Unit Tests (1)
-
check-skipped=Python Unit Tests (1)
-
check-success=Python Unit Tests (1)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral=Python Unit Tests (2)
-
check-skipped=Python Unit Tests (2)
-
check-success=Python Unit Tests (2)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral=Python Unit Tests (3)
-
check-skipped=Python Unit Tests (3)
-
check-success=Python Unit Tests (3)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral=Python Unit Tests (4)
-
check-skipped=Python Unit Tests (4)
-
check-success=Python Unit Tests (4)
-
-
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] -
label!=dont-merge
-
label!=squash
-
status-success=linters
- any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [🛡 GitHub branch protection]
-
check-success=linters
-
check-neutral=linters
-
check-skipped=linters
-
Rule: Automatic squash on CI success and review (merge)
-
#approved-reviews-by>=1
-
-closed
[📌 merge requirement] -
label=squash
-
status-success=Patch Test
-
status-success=Python Unit Tests (1)
-
status-success=Python Unit Tests (2)
-
status-success=Python Unit Tests (3)
-
status-success=Sider
- any of: [🛡 GitHub branch protection]
-
check-neutral=Patch Test
-
check-skipped=Patch Test
-
check-success=Patch Test
-
- any of: [🛡 GitHub branch protection]
-
check-neutral=Python Unit Tests (1)
-
check-skipped=Python Unit Tests (1)
-
check-success=Python Unit Tests (1)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral=Python Unit Tests (2)
-
check-skipped=Python Unit Tests (2)
-
check-success=Python Unit Tests (2)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral=Python Unit Tests (3)
-
check-skipped=Python Unit Tests (3)
-
check-success=Python Unit Tests (3)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral=Python Unit Tests (4)
-
check-skipped=Python Unit Tests (4)
-
check-success=Python Unit Tests (4)
-
-
-conflict
[📌 merge requirement] -
-draft
[📌 merge requirement] -
label!=dont-merge
-
status-success=linters
- any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
- any of: [🛡 GitHub branch protection]
-
check-success=linters
-
check-neutral=linters
-
check-skipped=linters
-
💖 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: Auto-close PRs on stable branch (close, comment)
- all of:
- any of:
-
base=version-12
-
base=version-13
-
base=version-14
-
base=version-15
-
base=version-16
-
- all of:
-
author!=ankush
-
author!=deepeshgarg007
-
author!=frappe-pr-bot
-
author!=gavindsouza
-
author!=mergify[bot]
-
author!=nabinhait
-
author!=rohitwaghchaure
-
author!=surajshetty3416
-
- any of:
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