Skip to content

ngit ci rerun ​

Rerun a completed native workflow, retaining its dependency bindings

Parent command: ngit ci

Related guide: CI

Usage ​

text
Usage: ngit ci rerun [OPTIONS] <COORDINATOR> <RESULT>

Arguments and options ​

InputDescriptionDetails
<COORDINATOR>Coordinator public key (npub or hex)required
<RESULT>Exact completed Workflow Result event id or neventrequired
--job <JOB>Rerun this job and its dependants; omit to restart every job—
--environment <JOB=SHA256[,URL]>Pin a native job's installed environment: JOB=SHA256[,MANIFEST-URL] JOB is its YAML key. SHA256 is the lowercase environment manifest hash, obtained from a provider offering or job evidence using ci inspect. Repeat for other jobs. The optional URL must name the same digest. This selects an installed environment; it does not install an image or remove resource requirements. Omitted jobs keep their normal pins.repeatable
--require <JOB=PATH:OP:JSON>Override a native job's resource/environment requirement (repeatable) JOB is its YAML key. PATH is a resource name or env/JSON-pointer. OP is eq, gte, lte or contains. JSON is an integer, boolean or quoted string; gte/lte require integers. Each path replaces its whole inherited constraint for that job; other paths and jobs are unchanged. Examples: --require 'build=memory-mib:gte:8192' (8 GiB RAM), --require 'build=vcpus:gte:4', --require 'build=env/configuration/guest/job-uid:eq:0'. Repeat gte/lte to set both bounds. Preserve JSON string quotes, e.g. --require 'build=some-resource:eq:"value"'. Duplicate job/path/operator triples are rejected. Requirements select offerings, not guest settings. Comparisons do not coerce types. In an env JSON Pointer write / as ~1 and ~ as ~0; in any path write : as %3A and % as %25. A published request is not proof that resources were allocated.repeatable
--rerun-dependenciesCompatibility flag; fresh manual triggers already rerun dependencies—
--offlineUse cached source result and repository authority only—
-n, --nsec <NSEC>nsec or hex private keyglobal; conflicts with --nbunksec <NBUNKSEC>, --nbunksec-file <PATH>, --nsec-file <PATH>, --signer <NPUB|ALIAS|NAME>
--nsec-file <PATH>Read an nsec or hex private key from a path resolving to a regular fileglobal; conflicts with --nbunksec <NBUNKSEC>, --nbunksec-file <PATH>, -n, --nsec <NSEC>, --signer <NPUB|ALIAS|NAME>
--nbunksec <NBUNKSEC>Established remote signer connection encoded as nbunksecglobal; conflicts with --nbunksec-file <PATH>, -n, --nsec <NSEC>, --nsec-file <PATH>, --signer <NPUB|ALIAS|NAME>
--nbunksec-file <PATH>Read an nbunksec connection from a path resolving to a regular fileglobal; conflicts with --nbunksec <NBUNKSEC>, -n, --nsec <NSEC>, --nsec-file <PATH>, --signer <NPUB|ALIAS|NAME>
--signer <NPUB|ALIAS|NAME>Use a configured signer by npub, profile, or cached Nostr display name for this commandglobal; conflicts with --nbunksec <NBUNKSEC>, --nbunksec-file <PATH>, -n, --nsec <NSEC>, --nsec-file <PATH>
-c, --customizeShow customization options via git configglobal
-d, --defaultsUse default values without prompting (non-interactive mode)global; conflicts with -i, --interactive
-i, --interactiveEnable prompts where supported (non-interactive by default)global; conflicts with -d, --defaults, --json
-f, --forceForce operations, bypass safety guardsglobal
-q, --quietSuppress progress and other non-essential outputglobal; conflicts with -v, --verbose
-v, --verboseShow detailed progress immediately and retain diagnosticsglobal; conflicts with -q, --quiet
--repo-relay-onlyOnly publish nostr events to repository relays, not user or default relaysglobal
--proactive-authAuthenticate to eligible relays on AUTH challenges before a request is rejectedglobal
--repo <REMOTE|NADDR|NOSTR-URL>Target repository for repo-scoped operations, overriding auto-detectionglobal
--jsonOutput machine-readable JSON on stdoutglobal; conflicts with -i, --interactive
-h, --helpPrint help (see a summary with '-h')—
-V, --versionPrint version—