Skip to content

升級 Minecraft 26.1.2 + 更新 GitHub Actions SHA pin - #476

Draft
jimchen5209 wants to merge 26 commits into
masterfrom
26.1.2
Draft

升級 Minecraft 26.1.2 + 更新 GitHub Actions SHA pin#476
jimchen5209 wants to merge 26 commits into
masterfrom
26.1.2

fix: try disable hardlink only

0170867
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Aug 4, 2026 in 5s

2 potential rules

Rule: Automatic merge on approval (queue)

  • #approved-reviews-by>=2
  • -draft [📌 queue requirement]
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue rule default]
      • github-review-approved [🛡 GitHub branch protection]
      • all of:
        • check-success = Build
        • check-success = Docker-image
      • any of: [🛡 GitHub branch protection]
        • check-success = Build
        • check-neutral = Build
        • check-skipped = Build
      • any of: [🛡 GitHub branch protection]
        • check-success = Docker-image
        • check-neutral = Docker-image
        • check-skipped = Docker-image
      • any of: [🛡 GitHub branch protection]
        • check-neutral = Mergify Merge Protections
        • check-skipped = Mergify Merge Protections
        • check-success = Mergify Merge Protections
  • #changes-requested-reviews-by=0
  • #review-requested=0
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • base=master
  • check-success=Build
  • check-success=Docker-image
  • label!=status: blocked
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 queue requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections

Rule: Automatic merge on ready label (queue)

  • -draft [📌 queue requirement]
  • label=status: ready to merge
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue rule default]
      • github-review-approved [🛡 GitHub branch protection]
      • all of:
        • check-success = Build
        • check-success = Docker-image
      • any of: [🛡 GitHub branch protection]
        • check-success = Build
        • check-neutral = Build
        • check-skipped = Build
      • any of: [🛡 GitHub branch protection]
        • check-success = Docker-image
        • check-neutral = Docker-image
        • check-skipped = Docker-image
      • any of: [🛡 GitHub branch protection]
        • check-neutral = Mergify Merge Protections
        • check-skipped = Mergify Merge Protections
        • check-success = Mergify Merge Protections
  • #changes-requested-reviews-by=0
  • #review-requested=0
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • base=master
  • check-success=Build
  • check-success=Docker-image
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 queue requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections

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