Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: incorrect qty after transaction in SLE (backport #43103) (backport #43104) #43108

Merged
merged 1 commit into from
Sep 7, 2024

fix: incorrect qty after transaction in SLE (backport #43103) (#43104)

f054261
Select commit
Loading
Failed to load commit list.
Merged

fix: incorrect qty after transaction in SLE (backport #43103) (backport #43104) #43108

fix: incorrect qty after transaction in SLE (backport #43103) (#43104)
f054261
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 24, 2024 in 0s

6 potential rules

⚠️ The pull request has been merged by @rohitwaghchaure

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 [🛡 GitHub branch protection]
  • #approved-reviews-by>=1
  • -closed [📌 merge requirement]
  • status-success=Semantic Pull Request
  • status-success=Sider
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • label!=dont-merge
  • 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=linters
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Automatic squash on CI success and review (merge)

  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #approved-reviews-by>=1
  • -closed [📌 merge requirement]
  • label=squash
  • status-success=Sider
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • label!=dont-merge
  • status-success=Patch Test
  • status-success=Python Unit Tests (1)
  • status-success=Python Unit Tests (2)
  • status-success=Python Unit Tests (3)
  • status-success=linters
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

💖  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:
    • all of:
      • author!=mergify[bot]
      • author!=ankush
      • author!=deepeshgarg007
      • author!=frappe-pr-bot
      • author!=gavindsouza
      • author!=nabinhait
      • author!=rohitwaghchaure
      • author!=surajshetty3416
    • any of:
      • base=version-14
      • base=version-12
      • base=version-13
      • base=version-15
      • base=version-16
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