moira: a first CI configuration, derived from this repository #7
Loading…
Reference in a new issue
No description provided.
Delete branch "moira/setup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
moira derived this configuration from the repository itself. Nothing here is moira's opinion about your project: the threads come from
moira-modules' detection reading your own manifests.It asks for read access only. No derived thread declares a write-level permission.
Threads this adds
auditPlanned by the
audittrait for the repository root, built byaudit.Options detection supplied:
paths,run. Everything else came from the constructor's own defaults.Permissions: contents
read, issuesnone.ciPlanned by the
rustdetector for the repository root, built byrustCi.Permissions: contents
read, issuesnone.Planned, and skipped
Detection found these and left them out. Each one is waiting on something no manifest can supply.
relock— not addedPlanned by
renovatefor.. It needscommitEmail, which nothing in the repository supplies.To enable it:
What this does not add
No
moiraFlake. That is a resource commitment — everypackages.*andchecks.*output built on every commit — and it is yours to make deliberately rather than to discover. The derived threads work without it. To add it later, outsideeachDefaultSystem:What this preview was computed from
git+https://git.hydrar.de/jmarya/moira-modulesatd05478464830c39f78dd741dccc04971029115ab, which is whatflake.lockpins.rustat..flake.nix; the one here declares threads and builds nothing.Before you merge
moira/setup, not the default branch.nix eval .#moiraExplain --jsonand pass options tofromProject. Everything above came out of that one evaluation.