Skip to content

Bump release-drafter/release-drafter from 5.19.0 to 6.1.0

79366f3
Select commit
Loading
Failed to load commit list.
Open

Bump release-drafter/release-drafter from 5.19.0 to 6.1.0 #3

Bump release-drafter/release-drafter from 5.19.0 to 6.1.0
79366f3
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jan 20, 2025 in 2s

1 potential rule

Rule: Delete head branch after merge (delete_head_branch)

  • closed [📌 delete_head_branch requirement]
  • merged

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

🚀  You can help us by becoming a sponsor!


3 not applicable rules

Rule: Request reviews and label Stewards' PRs (label, request_reviews)

  • any of:
    • author=scala-steward
    • author=trace4cats-steward[bot]

Rule: Merge Stewards' PRs (merge)

  • all of:
    • check-success~=Test \(ubuntu-latest, 2\.12\.\d+, temurin@17\)
    • check-success~=Test \(ubuntu-latest, 2\.12\.\d+, temurin@8\)
    • check-success~=Test \(ubuntu-latest, 2\.13\.\d+, temurin@17\)
    • check-success~=Test \(ubuntu-latest, 2\.13\.\d+, temurin@8\)
    • check-success~=Test \(ubuntu-latest, 3\.\d+\.\d+, temurin@17\)
    • check-success~=Test \(ubuntu-latest, 3\.\d+\.\d+, temurin@8\)
  • any of:
    • author=scala-steward
    • author=trace4cats-steward[bot]
  • any of:
    • #approved-reviews-by>=1
    • body~=labels:.*semver-patch
    • all of:
      • any of:
        • files=.scalafmt.conf
        • files=project/build.properties
        • files=project/plugins.sbt
      • #files=1
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Merge PRs via Mergify to skip the release step on CI (merge)

  • all of:
    • label=ready-to-merge
    • label=skip-release
  • all of:
    • check-success~=Test \(ubuntu-latest, 2\.12\.\d+, temurin@17\)
    • check-success~=Test \(ubuntu-latest, 2\.12\.\d+, temurin@8\)
    • check-success~=Test \(ubuntu-latest, 2\.13\.\d+, temurin@17\)
    • check-success~=Test \(ubuntu-latest, 2\.13\.\d+, temurin@8\)
    • check-success~=Test \(ubuntu-latest, 3\.\d+\.\d+, temurin@17\)
    • check-success~=Test \(ubuntu-latest, 3\.\d+\.\d+, temurin@8\)
  • any of:
    • author=catostrophe
    • author=janstenpickle
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
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