Skip to content

WIP Fix usage of cc.tools.cc as string vs struct

c32fa18
Select commit
Loading
Failed to load commit list.
Draft

Remove calls to resolve_tools #2406

WIP Fix usage of cc.tools.cc as string vs struct
c32fa18
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded May 5, 2026 in 0s

2 potential rules

Rule: remove from merge-queue after merge (label)

  • merged

Rule: automatic merge (queue)

  • -draft [📌 queue requirement]
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue rule default]
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • label=merge-queue
      • any of: [🛡 GitHub branch protection]
        • check-neutral = all_ci_tests
        • check-skipped = all_ci_tests
        • check-success = all_ci_tests
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • base=master
      • any of: [🛡 GitHub branch protection]
        • check-success = deploy/netlify
        • check-neutral = deploy/netlify
        • check-skipped = deploy/netlify
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • any of: [📌 queue -> 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