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

Setup stages #4618

Merged
merged 6 commits into from Dec 21, 2017

message to not include commits in app setup stages

b8576c1
Select commit
Failed to load commit list.
Merged

Setup stages #4618

message to not include commits in app setup stages
b8576c1
Select commit
Failed to load commit list.
Mergify / Summary succeeded May 24, 2023 in 1s

5 potential rules

⚠️ The pull request has been merged by @nabinhait

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

  • #approved-reviews-by>=1
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Patch
    • check-skipped=Patch
    • check-success=Patch
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Frappe Linter
    • check-skipped=Frappe Linter
    • check-success=Frappe Linter
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Semantic Commits
    • check-skipped=Semantic Commits
    • check-success=Semantic Commits
  • any of: [🛡 GitHub branch protection]
    • check-neutral=UI Tests (Cypress) (1)
    • check-skipped=UI Tests (Cypress) (1)
    • check-success=UI Tests (Cypress) (1)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=UI Tests (Cypress) (2)
    • check-skipped=UI Tests (Cypress) (2)
    • check-success=UI Tests (Cypress) (2)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=UI Tests (Cypress) (3)
    • check-skipped=UI Tests (Cypress) (3)
    • check-success=UI Tests (Cypress) (3)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Unit Tests (mariadb, 1)
    • check-skipped=Unit Tests (mariadb, 1)
    • check-success=Unit Tests (mariadb, 1)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Unit Tests (mariadb, 2)
    • check-skipped=Unit Tests (mariadb, 2)
    • check-success=Unit Tests (mariadb, 2)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Unit Tests (postgres, 1)
    • check-skipped=Unit Tests (postgres, 1)
    • check-success=Unit Tests (postgres, 1)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Unit Tests (postgres, 2)
    • check-skipped=Unit Tests (postgres, 2)
    • check-success=Unit Tests (postgres, 2)
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • -draft [:pushpin: merge requirement]
  • -mergify-configuration-changed [:pushpin: merge -> allow_merging_configuration_change setting requirement]
  • label!=dont-merge
  • label!=squash

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

  • #approved-reviews-by>=1
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • label=squash
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Patch
    • check-skipped=Patch
    • check-success=Patch
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Frappe Linter
    • check-skipped=Frappe Linter
    • check-success=Frappe Linter
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Semantic Commits
    • check-skipped=Semantic Commits
    • check-success=Semantic Commits
  • any of: [🛡 GitHub branch protection]
    • check-neutral=UI Tests (Cypress) (1)
    • check-skipped=UI Tests (Cypress) (1)
    • check-success=UI Tests (Cypress) (1)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=UI Tests (Cypress) (2)
    • check-skipped=UI Tests (Cypress) (2)
    • check-success=UI Tests (Cypress) (2)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=UI Tests (Cypress) (3)
    • check-skipped=UI Tests (Cypress) (3)
    • check-success=UI Tests (Cypress) (3)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Unit Tests (mariadb, 1)
    • check-skipped=Unit Tests (mariadb, 1)
    • check-success=Unit Tests (mariadb, 1)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Unit Tests (mariadb, 2)
    • check-skipped=Unit Tests (mariadb, 2)
    • check-success=Unit Tests (mariadb, 2)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Unit Tests (postgres, 1)
    • check-skipped=Unit Tests (postgres, 1)
    • check-success=Unit Tests (postgres, 1)
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Unit Tests (postgres, 2)
    • check-skipped=Unit Tests (postgres, 2)
    • check-success=Unit Tests (postgres, 2)
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • -draft [:pushpin: merge requirement]
  • -mergify-configuration-changed [:pushpin: merge -> allow_merging_configuration_change setting requirement]
  • label!=dont-merge

Rule: backport to develop (backport)

  • label="backport develop"
  • merged [:pushpin: backport requirement]

Rule: backport to version-13-hotfix (backport)

  • label="backport version-13-hotfix"
  • merged [:pushpin: backport requirement]

Rule: backport to version-14-hotfix (backport)

  • label="backport version-14-hotfix"
  • merged [:pushpin: backport requirement]

💖  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
    • all of:
      • author!=ankush
      • author!=deepeshgarg007
      • author!=frappe-pr-bot
      • author!=mergify[bot]
      • author!=surajshetty3416
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