Skip to content

Merge branch 'main' into feature/quantization-modifier-ddp

87f4b0d
Select commit
Loading
Failed to load commit list.
Open

[Distributed] Extend QuantizationModifier to support distributed activation calibration #2391

Merge branch 'main' into feature/quantization-modifier-ddp
87f4b0d
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Mar 3, 2026 in 0s

3 rules match and 3 potential rules

Rule: Automatically merge when ready (queue)

  • #approved-reviews-by>=2
  • check-success=base-tests (3.10)
  • check-success=base-tests (3.13)
  • check-success=markdown-link-check
  • check-success=pytorch-tests (3.10)
  • check-success=pytorch-tests (3.13)
  • check-success=quality-check
  • check-success=ready-label-check
  • check-success=transformers-tests
  • label=ready
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
      • check-success=base-tests (3.10)
      • check-success=base-tests (3.13)
      • check-success=markdown-link-check
      • check-success=pytorch-tests (3.10)
      • check-success=pytorch-tests (3.13)
      • check-success=quality-check
      • check-success=transformers-tests
      • any of: [🛡 GitHub branch protection]
        • check-neutral = transformers-tests
        • check-skipped = transformers-tests
        • check-success = transformers-tests
      • any of: [🛡 GitHub branch protection]
        • check-neutral = base-tests (3.10)
        • check-skipped = base-tests (3.10)
        • check-success = base-tests (3.10)
      • any of: [🛡 GitHub branch protection]
        • check-neutral = base-tests (3.13)
        • check-skipped = base-tests (3.13)
        • check-success = base-tests (3.13)
      • any of: [🛡 GitHub branch protection]
        • check-neutral = pytorch-tests (3.10)
        • check-skipped = pytorch-tests (3.10)
        • check-success = pytorch-tests (3.10)
      • any of: [🛡 GitHub branch protection]
        • check-neutral = pytorch-tests (3.13)
        • check-skipped = pytorch-tests (3.13)
        • check-success = pytorch-tests (3.13)
      • any of: [🛡 GitHub branch protection]
        • check-neutral = ready-label-check
        • check-skipped = ready-label-check
        • check-success = ready-label-check
      • any of: [🛡 GitHub branch protection]
        • check-neutral = markdown-link-check
        • check-skipped = markdown-link-check
        • check-success = markdown-link-check
      • any of: [🛡 GitHub branch protection]
        • check-neutral = quality-check
        • check-skipped = quality-check
        • check-success = quality-check
      • check-success=DCO
      • any of: [🛡 GitHub branch protection]
        • check-success = DCO
        • check-neutral = DCO
        • check-skipped = DCO
  • -closed [📌 queue requirement]
  • -conflict
  • -conflict [📌 queue requirement]
  • -draft
  • -draft [📌 queue requirement]
  • base=main
  • check-success=DCO
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

✅ Rule: label-documentation (label)

  • -closed
  • label != stale
  • any of:
    • files~=^examples/
    • files~=^[^/]+\.md$
    • files~=^docs/

Rule: ping author on conflicts and add 'needs-rebase' label (comment, label)

  • conflict
  • -closed
  • label != stale

✅ Rule: remove 'needs-rebase' label when conflict is resolved (label)

  • -closed
  • -conflict

Rule: add quality-failed label (comment, label)

  • check-failure = quality-check
  • -closed
  • label != stale

✅ Rule: remove quality-failed label (label)

  • -check-failure = quality-check
  • -closed
  • label != stale

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

🚀  You can help us by becoming a sponsor!


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