No description
  • Nix 67.1%
  • Shell 32.9%
Find a file
2026-05-16 16:20:45 +00:00
.forgejo/workflows ci: use nix forgejo runner 2026-05-16 15:01:37 +01:00
pkgs update package pins 2026-05-16 16:20:45 +00:00
scripts initial edge packages flake 2026-05-16 10:05:58 +01:00
.gitignore initial edge packages flake 2026-05-16 10:05:58 +01:00
flake.lock initial edge packages flake 2026-05-16 10:05:58 +01:00
flake.nix initial edge packages flake 2026-05-16 10:05:58 +01:00
README.md ci: use nix forgejo runner 2026-05-16 15:01:37 +01:00

edge-pkgs

Personal flake for fast-moving packages that should update independently of the main NixOS configuration.

Packages

  • claude-code
  • codex
  • opencode-desktop
  • t3code

Usage

inputs.edge-pkgs = {
  url = "git+ssh://git@forgejo.example.com/hegdeatri/edge-pkgs.git";
  inputs.nixpkgs.follows = "nixpkgs";
};

Then install a package with:

inputs.edge-pkgs.packages.${pkgs.stdenv.hostPlatform.system}.claude-code

Updating

./scripts/update-all.sh
nix flake check

Forgejo Actions runs the same updater on a schedule and commits changes when package pins change.

Forgejo Actions

The workflow expects a Forgejo runner label named nix. That label should point to a job image with Nix preinstalled.

For the existing medusa runner, this matches the registered label:

nix:docker://forgejo-nix-act:latest

Repository Actions must be enabled in Forgejo, and the workflow token needs permission to push commits back to the repository.