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 semgrep from 1.94.0 to 1.95.0 #107

Merged
merged 1 commit into from
Nov 1, 2024

chore(deps-dev): bump semgrep from 1.94.0 to 1.95.0

334265d
Select commit
Loading
Failed to load commit list.
Merged

chore(deps-dev): bump semgrep from 1.94.0 to 1.95.0 #107

chore(deps-dev): bump semgrep from 1.94.0 to 1.95.0
334265d
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 1, 2024 in 0s

1 rule matches and 4 potential rules

‼️ Action Required ‼️

**The configuration uses the deprecated speculative_checks attribute in the queue_rules section. It has been replaced in favor of max_parallel_checks in the merge_queue section of the configuration.
For more information: https://docs.mergify.com/merge-queue/speculative-checks/
‼️ Action Required ‼️
The configuration uses the deprecated disallow_checks_interruption_from_queues attribute in the queue_rules section. This option has been replaced by allow_checks_interruption at the top level of the configuration file in the priority_rules section.
A brownout is planned on November 11th, 2024.
This option will be removed on December 11th, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#priority-rules

Rule: automatic merge (queue)

  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • base=main
  • label!=manual merge
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue lowprio]
      • #commits=1
      • author=dependabot[bot]
      • all of:
        • check-success=Test with Python 3.10
        • check-success=Test with Python 3.11
        • check-success=Test with Python 3.12
        • check-success=Test with Python 3.8
        • check-success=Test with Python 3.9
      • any of: [🛡 GitHub repository ruleset rule]
        • check-success = Mergify Merge Protections
        • check-neutral = Mergify Merge Protections
        • check-skipped = Mergify Merge Protections
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=1
      • #changes-requested-reviews-by=0
      • #review-requested=0
      • #review-threads-unresolved=0
      • all of:
        • check-success=Test with Python 3.10
        • check-success=Test with Python 3.11
        • check-success=Test with Python 3.12
        • check-success=Test with Python 3.8
        • check-success=Test with Python 3.9
      • any of: [🛡 GitHub repository ruleset rule]
        • check-success = Mergify Merge Protections
        • check-neutral = Mergify Merge Protections
        • check-skipped = Mergify Merge Protections

✅ Rule: dismiss reviews (dismiss_reviews)

Rule: warn on conflicts (comment, label)

  • -closed
  • conflict

Rule: label on unresolved (label)

  • #review-threads-unresolved>0

Rule: label on queued (label)

  • queue-position>=0

3 not applicable rules

Rule: request review (request_reviews)

  • -author=dependabot[bot]
  • -closed
  • -merged
  • #approved-reviews-by=0
  • #changes-requested-reviews-by=0
  • review-requested!=@devs
  • all of:
    • check-success=Test with Python 3.10
    • check-success=Test with Python 3.11
    • check-success=Test with Python 3.12
    • check-success=Test with Python 3.8
    • check-success=Test with Python 3.9

Rule: Clifus labels (label)

  • author=mergify-ci-bot
  • head~=^clifus/
  • title~=^chore: bump
  • base=main

Rule: Trivy label (label)

  • author=mergify-ci-bot
  • body~=New CVEs:
  • head=trivy/daily-report
  • base=main
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