superconfig/.github/workflows/ at 447b6da3fd77f00a2e4ee7de023accdac0eacaa3 · lass.pds.lassul.us/superconfig · Tangled

lass.pds.lassul.us / superconfig

0

This repository has no description

0

superconfig / .github / workflows

4 files

at 447b6da3fd77f00a2e4ee7de023accdac0eacaa3

Hermes .github.update-pkgs: let PRs run ci themselves and merge via auto-merge 6d ago

.github.update-pkgs: let PRs run ci themselves and merge via auto-merge Branches, PRs and auto-merge now use the UPDATE_PKGS_TOKEN repo secret instead of GITHUB_TOKEN, so the normal pull_request ci.yml run (with the farm build) shows up on each PR and GitHub merges it with a merge commit once the ruleset is met. The serial verify job (rebase, dispatch ci.yml, wait, merge) and the final ci dispatch on master are gone: the auto-merge counts as the token's, so the push to master triggers ci.yml itself. UPDATE_PKGS_TOKEN: fine-grained PAT (or GitHub App token) for this repo with Contents: read/write, Pull requests: read/write and Workflows: read/write (force-pushing an update branch rebased over master commits that touched .github/workflows is refused without it). The repo needs "Allow auto-merge" enabled. The workflow fails early if the secret is missing.

6 days ago

.github: build all machines with the farm in the ci check, one job per machine ci.yml calls farm.yml (now reusable) instead of the eval-only nixos-* checks, which are gone from flake.nix. The farm job is only the coordinator (scheduler + envoy, which now requires the farm client cert, reachable over iroh). Each machine job joins as a builder, evaluates its machine, builds the toplevel through the farm and leaves when done; its outputs are in niks3 by then. ci runs for master pushes, PRs and dispatches; a newer run for the same ref cancels the older one, farms of different refs queue FIFO (queue: max). update-pkgs verifies PRs with ci.yml alone.

6 days ago

unmaintained-graph.yml

ci: publish unmaintained-graph to GitHub Pages

2 weeks ago

update-pkgs.yml

.github.update-pkgs: let PRs run ci themselves and merge via auto-merge Branches, PRs and auto-merge now use the UPDATE_PKGS_TOKEN repo secret instead of GITHUB_TOKEN, so the normal pull_request ci.yml run (with the farm build) shows up on each PR and GitHub merges it with a merge commit once the ruleset is met. The serial verify job (rebase, dispatch ci.yml, wait, merge) and the final ci dispatch on master are gone: the auto-merge counts as the token's, so the push to master triggers ci.yml itself. UPDATE_PKGS_TOKEN: fine-grained PAT (or GitHub App token) for this repo with Contents: read/write, Pull requests: read/write and Workflows: read/write (force-pushing an update branch rebased over master commits that touched .github/workflows is refused without it). The repo needs "Allow auto-merge" enabled. The workflow fails early if the secret is missing.

6 days ago