Skip to content

fix: Dockerfile build without gcc #413

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
mamirpanah wants to merge 3 commits into
base: umee
Choose a base branch
from

Merge branch 'umee' into umee

51a1703
Select commit
Loading
Failed to load commit list.
Open

fix: Dockerfile build without gcc #413

Merge branch 'umee' into umee
51a1703
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 5, 2025 in 4s

no rules match, no planned actions

3 not applicable rules

Rule: Automatic merge on approval (merge)

  • base=main
  • any of: [🛡 GitHub branch protection]
    • check-neutral = test-unit
    • check-skipped = test-unit
    • check-success = test-unit
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • label=A:Automerge
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = Run PR Title Linter
    • check-neutral = Run PR Title Linter
    • check-skipped = Run PR Title Linter

Rule: Automatic merge on approval (queue)

  • base=main
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • any of: [🛡 GitHub branch protection]
        • check-neutral = test-unit
        • check-skipped = test-unit
        • check-success = test-unit
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success = Run PR Title Linter
        • check-neutral = Run PR Title Linter
        • check-skipped = Run PR Title Linter
  • #approved-reviews-by>=1
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • label=A:Automerge
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Backport changes to umee branch (backport)

  • base=main
  • label=S:backport/umee
  • merged [📌 backport requirement]
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