Skip to content

Update flake input: home-manager

b79c315
Select commit
Loading
Failed to load commit list.
Open

Update flake input: home-manager #375

Update flake input: home-manager
b79c315
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded May 8, 2026 in 0s

1 rule matches and 2 potential rules

✅ Rule: self-assign PRs (assign)

  • #assignee=0
  • -closed
  • -merged

Rule: queue human PRs (queue)

  • #approved-reviews-by>=1
  • all of:
    • label!=flake-update
    • author!=github-actions[bot]
    • author!=mergify[bot]
    • author!=renovate[bot]
    • author!=vanixiets-flake-updater[bot]
  • all of:
    • check-success=build-nix-images (codenix, aarch64-linux, ubuntu-24.04-arm)
    • check-success=build-nix-images (codenix, x86_64-linux, ubuntu-latest)
    • check-success=build-nix-images (ghanix, aarch64-linux, ubuntu-24.04-arm)
    • check-success=build-nix-images (ghanix, x86_64-linux, ubuntu-latest)
    • check-success=build-nix-images (jupnix, aarch64-linux, ubuntu-24.04-arm)
    • check-success=build-nix-images (jupnix, x86_64-linux, ubuntu-latest)
    • check-success=build-nix-images (nixpod, aarch64-linux, ubuntu-24.04-arm)
    • check-success=build-nix-images (nixpod, x86_64-linux, ubuntu-latest)
    • check-success=publish-manifests (codenix)
    • check-success=publish-manifests (ghanix)
    • check-success=publish-manifests (jupnix)
    • check-success=publish-manifests (nixpod)
    • any of:
      • check-skipped=flake-check
      • check-success=flake-check
    • check-success=check-fast-forward
    • check-success=secrets-scan
    • check-success=set-variables
    • any of:
      • check-success=preview-release-version
      • check-skipped=preview-release-version
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • all of:
    • -conflict
    • -draft
    • label!=work-in-progress
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue rule default]
      • -conflict

Rule: queue bot PRs (queue)

  • #approved-reviews-by>=1
  • all of:
    • check-success=build-nix-images (codenix, aarch64-linux, ubuntu-24.04-arm)
    • check-success=build-nix-images (codenix, x86_64-linux, ubuntu-latest)
    • check-success=build-nix-images (ghanix, aarch64-linux, ubuntu-24.04-arm)
    • check-success=build-nix-images (ghanix, x86_64-linux, ubuntu-latest)
    • check-success=build-nix-images (jupnix, aarch64-linux, ubuntu-24.04-arm)
    • check-success=build-nix-images (jupnix, x86_64-linux, ubuntu-latest)
    • check-success=build-nix-images (nixpod, aarch64-linux, ubuntu-24.04-arm)
    • check-success=build-nix-images (nixpod, x86_64-linux, ubuntu-latest)
    • check-success=publish-manifests (codenix)
    • check-success=publish-manifests (ghanix)
    • check-success=publish-manifests (jupnix)
    • check-success=publish-manifests (nixpod)
    • any of:
      • check-skipped=flake-check
      • check-success=flake-check
    • check-success=check-fast-forward
    • check-success=secrets-scan
    • check-success=set-variables
    • any of:
      • check-success=preview-release-version
      • check-skipped=preview-release-version
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • all of:
    • -conflict
    • -draft
    • label!=work-in-progress
  • all of:
    • any of:
      • label=flake-update
      • author=github-actions[bot]
      • author=mergify[bot]
      • author=renovate[bot]
      • author=vanixiets-flake-updater[bot]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue rule bot-updates]
      • -conflict

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