Below you will find pages that utilize the taxonomy term “Spotdemo4”
August 15, 2026
nix init
Version updated for https://github.com/spotdemo4/nix-init to version v1.65.0.
This action is used across all versions by 4 repositories. Action Type This is a Composite action.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The nix-init action initializes Nix-based repositories by automating common setup steps such as creating GitHub app tokens, checking out the repository, setting up Git user and environment, installing Nix, configuring Nix settings based on a flake, and handling caching. It is designed to streamline the process for developers working with Nix in various environments, including self-hosted runners like Forgejo and GitHub Actions. The action also allows users to specify different shells from a flake for development purposes.
August 14, 2026
nix init
Version updated for https://github.com/spotdemo4/nix-init to version v1.64.0.
This action is used across all versions by 4 repositories. Action Type This is a Composite action.
Go to the GitHub Marketplace to find the latest changes.
Action Summary This GitHub Action initializes Nix-based repositories by automating common setup tasks such as creating a GitHub app token, checking out the repository, setting up Git user information, configuring an optimal Nix environment, installing Nix, and optionally setting caching. It works with self-hosted/gitea/forgejo action runners and is designed to save time by reducing repetitive configuration steps across multiple workflows.
August 1, 2026
nix init
Version updated for https://github.com/spotdemo4/nix-init to version v1.63.0.
This action is used across all versions by 4 repositories. Action Type This is a Composite action.
Go to the GitHub Marketplace to find the latest changes.
Action Summary This GitHub Action initializes Nix-based repositories by automating common setup tasks such as creating a GitHub app token, checking out the repository, setting up Git user information, installing Nix, configuring it based on flake settings, and handling caching. It supports various platforms like GitHub, Gitea, and Forgejo and can be used to streamline workflows by reducing repetitive code across different jobs.