Skip to content

refactor: replace install-common.sh with declarative artifact system - #473

Merged
mergify[bot] merged 21 commits into
mainfrom
unify-install-scripts
Jul 7, 2026
Merged

refactor: replace install-common.sh with declarative artifact system#473
mergify[bot] merged 21 commits into
mainfrom
unify-install-scripts

cache artifact downloads across container builds

eecbac6
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jul 7, 2026 in 2s

6 potential rules

commit_message_template is deprecated and will be removed on 2026-09-30. Use the declarative commit_message_format instead: https://docs.mergify.com/workflow/actions/merge#migrating-from-commit_message_template

Rule: keep PRs up to date with main (update)

  • #commits-behind > 0 [📌 update requirement]
  • -closed
  • -closed [📌 update requirement]
  • -merged
  • -conflict
  • -conflict [📌 update requirement]
  • -draft
  • label!=do-not-merge
  • queue-position = -1 [📌 update requirement]

Rule: auto-merge github-deps (merge)

  • -closed [📌 merge requirement]
  • title~=chore\(github-deps\)
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • check-success=pre-commit
  • check-success=title-check
  • github-review-approved [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub repository ruleset rule ODH-Require-PRs]
  • label!=do-not-merge
  • label!=needs-rebase
  • any of:
    • base=main
    • base~=^release-
    • base~=^rhoai-v
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = pre-commit
    • check-neutral = pre-commit
    • check-skipped = pre-commit
  • any of: [🛡 GitHub branch protection]
    • check-success = title-check
    • check-neutral = title-check
    • check-skipped = title-check

Rule: auto-merge (merge)

  • -closed [📌 merge requirement]
  • #approved-reviews-by>=2
  • #changes-requested-reviews-by=0
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • -title~=chore\(github-deps\)
  • check-success=pre-commit
  • check-success=title-check
  • github-review-approved [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub repository ruleset rule ODH-Require-PRs]
  • label!=do-not-merge
  • label!=needs-rebase
  • any of:
    • base=main
    • base~=^release-
    • base~=^rhoai-v
  • any of:
    • all of:
      • check-success~=build-test
      • any of:
        • files~=^Containerfile$
        • files~=^distribution/
        • files~=^\.github/actions/setup-vllm/action\.yml$
        • files~=^\.github/workflows/redhat-distro-container\.yml$
        • files~=^tests/
        • files~=^vllm/
    • all of:
      • -files~=^Containerfile$
      • -files~=^distribution/
      • -files~=^\.github/actions/setup-vllm/action\.yml$
      • -files~=^\.github/workflows/redhat-distro-container\.yml$
      • -files~=^tests/
      • -files~=^vllm/
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = pre-commit
    • check-neutral = pre-commit
    • check-skipped = pre-commit
  • any of: [🛡 GitHub branch protection]
    • check-success = title-check
    • check-neutral = title-check
    • check-skipped = title-check

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

  • -closed
  • conflict

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

  • -closed
  • -conflict

Rule: remind about Konflux Dockerfile when Containerfile changes (comment)

  • -closed
  • files~=^Containerfile$

💖  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