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

chore(deps-dev): bump ejs from 3.1.9 to 3.1.10 #56

Merged
merged 1 commit into from
Jul 30, 2024

chore(deps-dev): bump ejs from 3.1.9 to 3.1.10

aeeedbd
Select commit
Loading
Failed to load commit list.
Merged

chore(deps-dev): bump ejs from 3.1.9 to 3.1.10 #56

chore(deps-dev): bump ejs from 3.1.9 to 3.1.10
aeeedbd
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jul 30, 2024 in 0s

1 rule matches and 2 potential rules

Rule: Auto-merge when checks pass and reviews are approved (merge)

  • -closed [📌 merge requirement]
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • all of:
    • #approved-reviews-by>=1
    • #changes-requested-reviews-by=0
    • check-success=SonarCloud Code Analysis
    • check-success=build
    • check-success=lint
    • check-success=test
    • label!=wontfix
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success=SonarCloud Code Analysis
    • check-neutral=SonarCloud Code Analysis
    • check-skipped=SonarCloud Code Analysis
  • any of: [🛡 GitHub branch protection]
    • check-success=build
    • check-neutral=build
    • check-skipped=build
  • any of: [🛡 GitHub branch protection]
    • check-success=lint
    • check-neutral=lint
    • check-skipped=lint
  • any of: [🛡 GitHub branch protection]
    • check-success=test
    • check-neutral=test
    • check-skipped=test

Rule: Auto-merge security updates when checks pass (merge)

  • -closed [📌 merge requirement]
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • author~=^dependabot(|-preview)\[bot\]$
  • check-success=SonarCloud Code Analysis
  • check-success=build
  • check-success=lint
  • check-success=test
  • label!=wontfix
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success=SonarCloud Code Analysis
    • check-neutral=SonarCloud Code Analysis
    • check-skipped=SonarCloud Code Analysis
  • any of: [🛡 GitHub branch protection]
    • check-success=build
    • check-neutral=build
    • check-skipped=build
  • any of: [🛡 GitHub branch protection]
    • check-success=lint
    • check-neutral=lint
    • check-skipped=lint
  • any of: [🛡 GitHub branch protection]
    • check-success=test
    • check-neutral=test
    • check-skipped=test

✅ Rule: Auto-merge security updates when checks pass (review)

  • author~=^dependabot(|-preview)\[bot\]$
  • check-success=SonarCloud Code Analysis
  • check-success=build
  • check-success=lint
  • check-success=test
  • label!=wontfix

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