Skip to content

Update sbt-github-actions to 0.29.0 #290

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.

Sign up for GitHub

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

Open
scala-steward wants to merge 2 commits into
base: master
Choose a base branch
from

Regenerate GitHub Actions workflow

575743b
Select commit
Loading
Failed to load commit list.
Open

Update sbt-github-actions to 0.29.0 #290

Regenerate GitHub Actions workflow
575743b
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 28, 2025 in 0s

1 rule matches and 2 potential rules

✅ Rule: Request reviews and label Steward's PRs (label, request_reviews)

  • author=scala-steward

Rule: Merge Steward's PRs (merge)

  • any of:
    • #approved-reviews-by>=1
    • body~=labels:.*semver-patch
    • all of:
      • #files=1
      • any of:
        • files=project/plugins.sbt
        • files=.scalafmt.conf
        • files=project/build.properties
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • author=scala-steward
  • 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: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Delete head branch after merge (delete_head_branch)

  • closed [📌 delete_head_branch requirement]
  • merged
1 not applicable rule

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

  • all of:
    • label=ready-to-merge
    • label=skip-release
  • any of:
    • author=catostrophe
    • author=janstenpickle
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • 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: [📌 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

View more details on Mergify