Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Does this action benefit from a nix cache? #201

@hey2022

Description

@hey2022

I saw recently in aa3e38e that the FlakeHub Cache was removed from this repository's update workflow.

I ask my question because I thought that a cache like magic-nix-cache would cache the inputs that are unpacked from running nix flake update. However, I found that the magic-nix-cache does nothing and the action spends a lot of time with stuff like unpacking _ into the Git cache.... I'm not sure what it means by the Git cache tho, could anyone clarify that?

Also when running the action i get messages like the following even though i just updated the flake.lock and no changes were made to the lock file.

GIT_COMMIT_MESSAGE is: Flake lock file updates:

• Updated input 'home-manager':
    'github:nix-community/home-manager/e90b28967cacc64de7fb8742314ed0d7d12f47c6?narHash=sha256-c1Rq5Hc4WZLKj1RkmjLFCcX4QHBwrL%2BDIZNMEHno7DU%3D' (2025-07-11)
  → 'github:nix-community/home-manager/bf893ad4cbf46610dd1b620c974f824e266cd1df?narHash=sha256-mCHfZhQKdTj2JhCFcqfOfa3uKZbwUkPQbd0/zPnhOE8%3D' (2025-07-13)

Is there a way to make this action not need to download and unpack all these inputs if nothing was updated in the lockfile?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions