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.

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

Jump to bottom

improvement: if no binary version in jar path try using build target info #6698

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

special case for scala lib and look for tasty files when discovering …

087940c
Select commit
Loading
Failed to load commit list.
Open

improvement: if no binary version in jar path try using build target info #6698

special case for scala lib and look for tasty files when discovering …
087940c
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Aug 26, 2024 in 0s

no rules match, no planned actions

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

🚀  You can help us by becoming a sponsor!

1 not applicable rule

Rule: Automatic merge on approval (merge)

  • author=scalameta-bot
  • check-success=Mill integration
  • check-success=Sbt-metals/scripted jdk8
  • check-success=Scala3 latest NIGHTLY cross test
  • check-success=macOS-latest jdk-17 unit tests 1 / 2
  • check-success=macOS-latest jdk-17 unit tests 2 / 2
  • check-success=ubuntu-latest jdk-8 unit tests 1 / 2
  • check-success=ubuntu-latest jdk-8 unit tests 2 / 2
  • label=library-update
  • label=semver-spec-patch
  • #approved-reviews-by>=1
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • check-success=Formatting
  • check-success=Gradle MacOS integration
  • check-success=Gradle integration
  • check-success=LSP integration tests
  • check-success=Maven integration
  • check-success=Sbt integration
  • check-success=Scala cross tests
  • check-success=Scalafix and docs
  • check-success=ubuntu-latest jdk-17 unit tests 1 / 2
  • check-success=ubuntu-latest jdk-17 unit tests 2 / 2
  • check-success=windows-latest jdk-17 unit tests 1 / 2
  • check-success=windows-latest jdk-17 unit tests 2 / 2
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success=Formatting
    • check-neutral=Formatting
    • check-skipped=Formatting
  • any of: [🛡 GitHub branch protection]
    • check-success=Scalafix and docs
    • check-neutral=Scalafix and docs
    • check-skipped=Scalafix and docs
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