Skip to content

Update scala-library, scala-reflect to 2.13.16

528bba1
Select commit
Loading
Failed to load commit list.
Closed

Update scala-library, scala-reflect to 2.13.16 #210

Update scala-library, scala-reflect to 2.13.16
528bba1
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jan 16, 2025 in 1s

1 rule matches and 3 potential rules

‼️ Action Required ‼️

The configuration uses the deprecated merge_method attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

βœ… Rule: Label Scala Steward PRs (label)

  • author=scala-steward

Rule: Merge dependency-update PRs (queue)

  • any of: [πŸ”€ queue conditions]
    • all of: [πŸ“Œ queue conditions of queue default]
      • any of: [πŸ›‘ GitHub branch protection]
        • check-neutral = build (2.13.15)
        • check-skipped = build (2.13.15)
        • check-success = build (2.13.15)
      • any of: [πŸ›‘ GitHub branch protection]
        • check-neutral = build (3.5.2)
        • check-skipped = build (3.5.2)
        • check-success = build (3.5.2)
      • #review-threads-unresolved = 0 [πŸ›‘ GitHub branch protection]
  • -closed [πŸ“Œ queue requirement]
  • -conflict [πŸ“Œ queue requirement]
  • -draft [πŸ“Œ queue requirement]
  • base=main
  • label=dependencies
  • any of: [πŸ“Œ queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Merge PRs using label (rebase) (queue)

  • label=ready-to-merge-rebase
  • any of: [πŸ”€ queue conditions]
    • all of: [πŸ“Œ queue conditions of queue default]
      • any of: [πŸ›‘ GitHub branch protection]
        • check-neutral = build (2.13.15)
        • check-skipped = build (2.13.15)
        • check-success = build (2.13.15)
      • any of: [πŸ›‘ GitHub branch protection]
        • check-neutral = build (3.5.2)
        • check-skipped = build (3.5.2)
        • check-success = build (3.5.2)
      • #review-threads-unresolved = 0 [πŸ›‘ GitHub branch protection]
  • #changes-requested-reviews-by=0
  • #review-requested=0
  • #review-threads-unresolved=0
  • -closed [πŸ“Œ queue requirement]
  • -conflict [πŸ“Œ queue requirement]
  • -draft [πŸ“Œ queue requirement]
  • base=main
  • any of: [πŸ“Œ queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Merge PRs using label (squash) (queue)

  • label=ready-to-merge-squash
  • any of: [πŸ”€ queue conditions]
    • all of: [πŸ“Œ queue conditions of queue default]
      • any of: [πŸ›‘ GitHub branch protection]
        • check-neutral = build (2.13.15)
        • check-skipped = build (2.13.15)
        • check-success = build (2.13.15)
      • any of: [πŸ›‘ GitHub branch protection]
        • check-neutral = build (3.5.2)
        • check-skipped = build (3.5.2)
        • check-success = build (3.5.2)
      • #review-threads-unresolved = 0 [πŸ›‘ GitHub branch protection]
  • #changes-requested-reviews-by=0
  • #review-requested=0
  • #review-threads-unresolved=0
  • -closed [πŸ“Œ queue requirement]
  • -conflict [πŸ“Œ queue requirement]
  • -draft [πŸ“Œ queue requirement]
  • base=main
  • any of: [πŸ“Œ queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

πŸ’–Β Β 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