Skip to content

[3.0.x] sbt 1.11.2 (was 1.11.1)

2e7d70c
Select commit
Loading
Failed to load commit list.
Merged

[3.0.x] Patch updates #359

[3.0.x] sbt 1.11.2 (was 1.11.1)
2e7d70c
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jun 10, 2025 in 1s

3 rules match and 3 potential rules

⚠️ The pull request has been merged by @mkurz

Rule: Merge PRs that are ready (queue)

  • #approved-reviews-by>=1
  • -closed [πŸ“Œ queue requirement]
  • label=status:merge-when-green
  • #changes-requested-reviews-by=0
  • #review-requested=0
  • -conflict [πŸ“Œ queue requirement]
  • -draft [πŸ“Œ queue requirement]
  • check-success~=/ Ready To Merge$
  • label!=status:block-merge
  • any of: [πŸ“Œ queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [πŸ”€ queue conditions]
    • all of: [πŸ“Œ queue conditions of queue default]
      • check-success~=/ Ready To Merge$
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = Finish / Ready To Merge
        • check-neutral = Finish / Ready To Merge
        • check-skipped = Finish / Ready To Merge

Rule: Merge (Rebase) PRs that are ready (queue)

  • #approved-reviews-by>=1
  • -closed [πŸ“Œ queue requirement]
  • label=status:merge-rebase-when-green
  • #changes-requested-reviews-by=0
  • #review-requested=0
  • -conflict [πŸ“Œ queue requirement]
  • -draft [πŸ“Œ queue requirement]
  • check-success~=/ Ready To Merge$
  • label!=status:block-merge
  • any of: [πŸ“Œ queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [πŸ”€ queue conditions]
    • all of: [πŸ“Œ queue conditions of queue rebase]
      • check-success~=/ Ready To Merge$
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = Finish / Ready To Merge
        • check-neutral = Finish / Ready To Merge
        • check-skipped = Finish / Ready To Merge

Rule: Merge (Squash) PRs that are ready (queue)

  • #approved-reviews-by>=1
  • -closed [πŸ“Œ queue requirement]
  • label=status:merge-squash-when-green
  • #changes-requested-reviews-by=0
  • #review-requested=0
  • -conflict [πŸ“Œ queue requirement]
  • -draft [πŸ“Œ queue requirement]
  • check-success~=/ Ready To Merge$
  • label!=status:block-merge
  • any of: [πŸ“Œ queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [πŸ”€ queue conditions]
    • all of: [πŸ“Œ queue conditions of queue squash]
      • check-success~=/ Ready To Merge$
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = Finish / Ready To Merge
        • check-neutral = Finish / Ready To Merge
        • check-skipped = Finish / Ready To Merge

βœ… Rule: Delete the PR branch and remove label after merge/close (delete_head_branch)

  • closed [πŸ“Œ delete_head_branch requirement]
  • any of:
    • closed
    • merged

βœ… Rule: Delete the PR branch and remove label after merge/close (label)

  • any of:
    • closed
    • merged

βœ… Rule: Labeling for Scala Steward PR's (label)

  • author=scala-steward

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