Skip to content

chore: formatting based on pre-commit

dd22e8f
Select commit
Loading
Failed to load commit list.
Open

fix: after mapping of stock entry map correct addresses and gstin #3998

chore: formatting based on pre-commit
dd22e8f
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Apr 3, 2026 in 0s

6 potential rules

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

  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • label!=dont-merge
  • label!=squash
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 merge requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🛡 GitHub branch protection]
    • check-success = CodeQL
    • check-neutral = CodeQL
    • check-skipped = CodeQL
  • any of: [🛡 GitHub branch protection]
    • check-success = Python Unit Tests
    • check-neutral = Python Unit Tests
    • check-skipped = Python Unit Tests
  • any of: [🛡 GitHub branch protection]
    • check-success = Analyze (python)
    • check-neutral = Analyze (python)
    • check-skipped = Analyze (python)
  • any of: [🛡 GitHub branch protection]
    • check-success = Analyze (javascript)
    • check-neutral = Analyze (javascript)
    • check-skipped = Analyze (javascript)
  • any of: [🛡 GitHub branch protection]
    • check-success = Check Commit Titles
    • check-neutral = Check Commit Titles
    • check-skipped = Check Commit Titles
  • 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 [🛡 GitHub branch protection]
  • #approved-reviews-by>=1
  • label=squash
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • label!=dont-merge
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 merge requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🛡 GitHub branch protection]
    • check-success = CodeQL
    • check-neutral = CodeQL
    • check-skipped = CodeQL
  • any of: [🛡 GitHub branch protection]
    • check-success = Python Unit Tests
    • check-neutral = Python Unit Tests
    • check-skipped = Python Unit Tests
  • any of: [🛡 GitHub branch protection]
    • check-success = Analyze (python)
    • check-neutral = Analyze (python)
    • check-skipped = Analyze (python)
  • any of: [🛡 GitHub branch protection]
    • check-success = Analyze (javascript)
    • check-neutral = Analyze (javascript)
    • check-skipped = Analyze (javascript)
  • any of: [🛡 GitHub branch protection]
    • check-success = Check Commit Titles
    • check-neutral = Check Commit Titles
    • check-skipped = Check Commit Titles
  • any of: [🛡 GitHub branch protection]
    • check-success = linters
    • check-neutral = linters
    • check-skipped = linters

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-16-hotfix (backport)

  • label="backport version-16-hotfix"
  • merged [📌 backport requirement]

💖  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: automatically merge backport if they pass tests (merge)

  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • author=mergify[bot]
  • base~=^version-
  • head~=^mergify/bp/
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • label!=conflicts
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 merge requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🛡 GitHub branch protection]
    • check-success = CodeQL
    • check-neutral = CodeQL
    • check-skipped = CodeQL
  • any of: [🛡 GitHub branch protection]
    • check-success = Python Unit Tests
    • check-neutral = Python Unit Tests
    • check-skipped = Python Unit Tests
  • any of: [🛡 GitHub branch protection]
    • check-success = Analyze (python)
    • check-neutral = Analyze (python)
    • check-skipped = Analyze (python)
  • any of: [🛡 GitHub branch protection]
    • check-success = Analyze (javascript)
    • check-neutral = Analyze (javascript)
    • check-skipped = Analyze (javascript)
  • any of: [🛡 GitHub branch protection]
    • check-success = Check Commit Titles
    • check-neutral = Check Commit Titles
    • check-skipped = Check Commit Titles
  • any of: [🛡 GitHub branch protection]
    • check-success = linters
    • check-neutral = linters
    • check-skipped = linters

Rule: Auto-close PRs on stable branch (close, comment)

  • any of:
    • base=version-14
    • base=version-15
    • base=version-16
  • all of:
    • author!=dependabot[bot]
    • author!=india-compliance-bot
    • author!=mergify[bot]
    • author!=sagarvora
    • author!=vorasmit
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