CI and devshell comments say what the config does: jobTimeout bounds jobs, coverage runs nightly, dead timeout keys removed
Job-level timeout-minutes is parsed but not enforced by this runner; only the runner's jobTimeout bounds a job. Also fixes the devshell coverage comment, the shellcheck job comment, an option description citing a script that is not in the repo, and comment file pointers that resolve to nothing.
This commit is contained in:
parent
fefc565794
commit
2644c0d5f9
7 changed files with 20 additions and 27 deletions
|
|
@ -143,8 +143,8 @@ in
|
|||
# view: the names and ports it answers on, the URLs it advertises, and the
|
||||
# client id it is registered under. What lives here is what the host running
|
||||
# it decides — which build it runs, how it is served, what it mirrors, and
|
||||
# where its host-local secrets sit. Same rule as ./swarm-victorialogs.nix,
|
||||
# and the renames are in ./deploy.nix with the rest.
|
||||
# where its host-local secrets sit. Same rule as ../swarm-victorialogs.nix,
|
||||
# and the renames are in ../deploy.nix with the rest.
|
||||
options.services.hyperhive.deploy.forgejo = {
|
||||
package = lib.mkOption {
|
||||
type = lib.types.package;
|
||||
|
|
|
|||
Loading…
Reference in a new issue