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: add filing period selection in gstr-1 beta #2766

Open
wants to merge 16 commits into
base: develop
Choose a base branch
from

fix: update logs with specific gstin

39bc072
Select commit
Loading
Failed to load commit list.
Open

fix: add filing period selection in gstr-1 beta #2766

fix: update logs with specific gstin
39bc072
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Dec 5, 2024 in 1s

5 potential rules

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

  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #approved-reviews-by>=1
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Python Unit Tests
    • check-skipped = Python Unit Tests
    • check-success = Python Unit Tests
  • #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: [🛡 GitHub branch protection]
    • check-success = CodeQL
    • check-neutral = CodeQL
    • check-skipped = CodeQL
  • 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
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Python Unit Tests
    • check-skipped = Python Unit Tests
    • check-success = Python Unit Tests
  • #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: [🛡 GitHub branch protection]
    • check-success = CodeQL
    • check-neutral = CodeQL
    • check-skipped = CodeQL
  • 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]

💖  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/
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Python Unit Tests
    • check-skipped = Python Unit Tests
    • check-success = Python Unit Tests
  • #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: [🛡 GitHub branch protection]
    • check-success = CodeQL
    • check-neutral = CodeQL
    • check-skipped = CodeQL
  • 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
  • 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