nixbot

builds
1treefmt v2.5.0traversed 274 files2emitted 230 files for processing3formatted 230 files (1 changed) in 1.004s4 M README.md5diff --git a/README.md b/README.md6index 6c2ebaa..656f051 1006447--- a/README.md8+++ b/README.md9@@ -138,14 +138,14 @@ legacy `buildbot-nix.toml`) in the root of whichever branch it's currently10 evaluating, parse it as TOML and apply the configuration specified. The11 following table illustrates the supported options.12 13-| | key | type | description | default | example |14-| :----------------------- | :------------------------- | :---------- | :-------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |15-| lock file | `lock_file` | `str` | dictates which lock file `nixbot` will use when evaluating your flake | `flake.lock` | have multiple lockfiles, one for `nixpkgs-stable`, one for `nixpkgs-unstable` or by default pin an input to a private repo, but have a lockfile with that private repo replaced by a public repo for CI |16-| attribute | `attribute` | `str` | which attribute in the flake to evaluate and build | `checks` | using a different attribute, like `hydraJobs` |17-| flake_dir | `flake_dir` | `str` | which directory the flake is located | `.` | using a different flake, like `./tests` |18-| effects on pull requests | `effects_on_pull_requests` | `bool` | run hercules-ci effects on pull requests | `false` | set to `true` to run effects on PRs |19-| effects branches | `effects_branches` | `list[str]` | glob patterns for additional branches that run effects | `[]` | `["staging", "release/*"]` |20-| legacy eval (deprecated) | `legacy_eval` | `bool` | evaluate `flake_dir#attribute` directly like buildbot-nix did: no `herculesCI`/`onPush` jobs, no build modifiers, attribute names keep their old unprefixed form | `false` | ease migration of existing repos that rely on the old attribute names; will be removed in a future release |21+| | key | type | description | default | example |22+| :----------------------- | :------------------------- | :---------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |23+| lock file | `lock_file` | `str` | dictates which lock file `nixbot` will use when evaluating your flake | `flake.lock` | have multiple lockfiles, one for `nixpkgs-stable`, one for `nixpkgs-unstable` or by default pin an input to a private repo, but have a lockfile with that private repo replaced by a public repo for CI |24+| attribute | `attribute` | `str` | which attribute in the flake to evaluate and build | `checks` | using a different attribute, like `hydraJobs` |25+| flake_dir | `flake_dir` | `str` | which directory the flake is located | `.` | using a different flake, like `./tests` |26+| effects on pull requests | `effects_on_pull_requests` | `bool` | run hercules-ci effects on pull requests | `false` | set to `true` to run effects on PRs |27+| effects branches | `effects_branches` | `list[str]` | glob patterns for additional branches that run effects | `[]` | `["staging", "release/*"]` |28+| legacy eval (deprecated) | `legacy_eval` | `bool` | evaluate `flake_dir#attribute` directly like buildbot-nix did: no `herculesCI`/`onPush` jobs, no build modifiers, attribute names keep their old unprefixed form | `false` | ease migration of existing repos that rely on the old attribute names; will be removed in a future release |29 30 By default, effects only run on the default branch. The `effects_branches` and31 `effects_on_pull_requests` settings are always read from the **default