moira: a first CI configuration, derived from this repository #7

Merged
jmarya merged 2 commits from moira/setup into main 2026-10-05 13:59:29 +00:00
Collaborator

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

audit

Planned by the audit trait for the repository root, built by audit.

Options detection supplied: paths, run. Everything else came from the constructor's own defaults.

Permissions: contents read, issues none.

ci

Planned by the rust detector for the repository root, built by rustCi.

Permissions: contents read, issues none.

Planned, and skipped

Detection found these and left them out. Each one is waiting on something no manifest can supply.

relock — not added

Planned by renovate for .. It needs commitEmail, which nothing in the repository supplies.

To enable it:

fromProject { src = self; relock.commitEmail = …; }

What this does not add

No moiraFlake. That is a resource commitment — every packages.* and checks.* 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, outside eachDefaultSystem:

moiraFlake = {
  include = [ "checks.*" "packages.*" ];
};

What this preview was computed from

  • Standard library: git+https://git.hydrar.de/jmarya/moira-modules at d05478464830c39f78dd741dccc04971029115ab, which is what flake.lock pins.
  • Detected: rust at ..
  • This repository had no flake.nix; the one here declares threads and builds nothing.

Before you merge

  • Merging is what starts anything. This branch runs nothing: moira reads a repository's configuration from its default branch, so until this is merged there is nothing to trigger.
  • This preview describes moira/setup, not the default branch.
  • To change what this generates, read nix eval .#moiraExplain --json and pass options to fromProject. Everything above came out of that one evaluation.
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 ### `audit` Planned by the `audit` trait for the repository root, built by `audit`. Options detection supplied: `paths`, `run`. Everything else came from the constructor's own defaults. Permissions: contents `read`, issues `none`. ### `ci` Planned by the `rust` detector for the repository root, built by `rustCi`. Permissions: contents `read`, issues `none`. ## Planned, and skipped Detection found these and left them out. Each one is waiting on something no manifest can supply. ### `relock` — not added Planned by `renovate` for `.`. It needs `commitEmail`, which nothing in the repository supplies. To enable it: ```nix fromProject { src = self; relock.commitEmail = …; } ``` ## What this does not add No `moiraFlake`. That is a resource commitment — every `packages.*` and `checks.*` 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, outside `eachDefaultSystem`: ```nix moiraFlake = { include = [ "checks.*" "packages.*" ]; }; ``` ## What this preview was computed from - Standard library: `git+https://git.hydrar.de/jmarya/moira-modules` at `d05478464830c39f78dd741dccc04971029115ab`, which is what `flake.lock` pins. - Detected: `rust` at `.`. - This repository had no `flake.nix`; the one here declares threads and builds nothing. ## Before you merge - **Merging is what starts anything.** This branch runs nothing: moira reads a repository's configuration from its default branch, so until this is merged there is nothing to trigger. - This preview describes `moira/setup`, not the default branch. - To change what this generates, read `nix eval .#moiraExplain --json` and pass options to `fromProject`. Everything above came out of that one evaluation.
jmarya merged commit 26815f4161 into main 2026-10-05 13:59:29 +00:00
jmarya deleted branch moira/setup 2026-10-05 13:59:29 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jmarya/ogpmeta!7
No description provided.