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.

Sign up for GitHub

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 vite from 5.4.6 to 5.4.7 in the npm_and_yarn group across 1 directory #79

Merged
merged 1 commit into from
Sep 25, 2024

chore(deps-dev): bump vite in the npm_and_yarn group across 1 directory

a00d9f3
Select commit
Loading
Failed to load commit list.
Merged

chore(deps-dev): bump vite from 5.4.6 to 5.4.7 in the npm_and_yarn group across 1 directory #79

chore(deps-dev): bump vite in the npm_and_yarn group across 1 directory
a00d9f3
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 25, 2024 in 1s

1 rule matches and 2 potential rules

⚠️ The pull request has been merged by @JoshTheWanderer

Rule: Auto-squash dependabot 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]
  • all of:
    • author~=^dependabot(|-preview)\[bot\]$
    • check-success=SonarCloud Code Analysis
    • check-success=build
    • check-success=lint
    • 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 = lint
    • check-neutral = lint
    • check-skipped = lint
  • any of: [🛡 GitHub branch protection]
    • check-success = build
    • check-neutral = build
    • check-skipped = build

✅ Rule: Auto-squash dependabot updates when checks pass (review)

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

Rule: Auto-squash when all checks pass and the PR has been 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
    • #review-requested=0
    • check-success=SonarCloud Code Analysis
    • check-success=build
    • check-success=lint
  • 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 = lint
    • check-neutral = lint
    • check-skipped = lint
  • any of: [🛡 GitHub branch protection]
    • check-success = build
    • check-neutral = build
    • check-skipped = build
2 not applicable rules

Rule: Ask an old fart to review the code (request_reviews)

  • -closed
  • author~=!^dependabot(|-preview)\[bot\]$
  • -draft

Rule: Get some more eyes on it (request_reviews)

  • -closed
  • author~=!^dependabot(|-preview)\[bot\]$
  • -draft
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

View more details on Mergify