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

[Snyk] Upgrade mysql2 from 3.11.5 to 3.12.0 #263

Merged
merged 4 commits into from
Jan 23, 2025

Merge branch 'main' into snyk-upgrade-7402b30213c41becc5be83e86d7e1bdc

803ecb7
Select commit
Loading
Failed to load commit list.
Merged

[Snyk] Upgrade mysql2 from 3.11.5 to 3.12.0 #263

Merge branch 'main' into snyk-upgrade-7402b30213c41becc5be83e86d7e1bdc
803ecb7
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jan 30, 2025 in 0s

10 potential rules

⚠️ The pull request has been closed by GitHub because its commits are also part of another pull request

Rule: Automatic merge during office hours + hotfix support (merge)

  • -closed [📌 merge requirement]
  • any of:
    • label = hotfix
    • schedule = Mon-Sat 08:00-21:00[Europe/Warsaw]
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 merge requirement]
    • check-success = Mergify Merge Protections
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
  • any of: [🛡 GitHub branch protection]
    • check-success = Mergify Merge Protections
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
  • any of: [🛡 GitHub branch protection]
    • check-success = CodeQL
    • check-neutral = CodeQL
    • check-skipped = CodeQL

Rule: Add a queue label when PR is queued (label)

  • queue-position > 0

Rule: Label Mergify Stacks PRs (label)

  • commits[0].commit_message ~= (?m)Change-Id:

Rule: Automatic merge (merge)

  • -closed [📌 merge requirement]
  • label = automerge
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 merge requirement]
    • check-success = Mergify Merge Protections
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
  • any of: [🛡 GitHub branch protection]
    • check-success = Mergify Merge Protections
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
  • any of: [🛡 GitHub branch protection]
    • check-success = CodeQL
    • check-neutral = CodeQL
    • check-skipped = CodeQL

Rule: Make sure PR are up to date before merging with rebase (rebase)

  • -closed [📌 rebase requirement]
  • -conflict [📌 rebase requirement]
  • queue-position = -1 [📌 rebase requirement]
  • any of:
    • #commits > 1 [📌 rebase requirement]
    • -linear-history [📌 rebase requirement]
    • #commits-behind > 0 [📌 rebase requirement]

Rule: Ping PR author when conflicting (comment)

  • -closed
  • conflict

Rule: Label conflicting pull requests (label)

  • -closed
  • conflict

Rule: Make sure PR are up to date before merging (update)

  • #commits-behind > 0 [📌 update requirement]
  • -closed [📌 update requirement]
  • -conflict [📌 update requirement]
  • queue-position = -1 [📌 update requirement]

Rule: Label first PR of Mergify Stacks PRs (label)

  • body ~= ^Change-Id:
  • -base ~= ^mergify_cli/

Rule: Notify when a PR is removed from the queue (comment)

  • queue-dequeue-reason != none
  • queue-dequeue-reason != pr-merged

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


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