ngit ci trigger
ask a coordinator to run one workflow once
Parent command: ngit ci
Related guide: CI
Upcoming command surface
This page is generated from an unreleased ngit commit. Its interface may change before the next release.
Usage
text
Usage: ngit ci trigger [OPTIONS] --workflow <PATH> <COORDINATOR> [COMMIT-ISH]Arguments and options
| Input | Description | Details |
|---|---|---|
<COORDINATOR> | Coordinator public key (npub or hex) | required |
<COMMIT-ISH> | Commit-ish to run; defaults to HEAD | — |
--workflow <PATH> | Path of the workflow file, as it exists at the resolved commit | required |
--ref <GIT-REF> | Git ref published as the run's context, e.g. refs/heads/main | — |
--offline | Use local cache only, skip network fetch | — |
-n, --nsec <NSEC> | nsec or hex private key | global; 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 file | global; conflicts with --nbunksec <NBUNKSEC>, --nbunksec-file <PATH>, -n, --nsec <NSEC>, --signer <NPUB|ALIAS|NAME> |
--nbunksec <NBUNKSEC> | established remote signer connection encoded as nbunksec | global; 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 file | global; conflicts with --nbunksec <NBUNKSEC>, -n, --nsec <NSEC>, --nsec-file <PATH>, --signer <NPUB|ALIAS|NAME> |
--signer <NPUB|ALIAS|NAME> | use a configured signer by npub, alias, or cached profile name for this command | global; conflicts with --nbunksec <NBUNKSEC>, --nbunksec-file <PATH>, -n, --nsec <NSEC>, --nsec-file <PATH> |
-c, --customize | show customization options via git config | global |
-d, --defaults | Use default values without prompting (non-interactive mode) | global; conflicts with -i, --interactive |
-i, --interactive | Enable interactive prompts (default behavior) | global; conflicts with -d, --defaults, --json |
-f, --force | Force operations, bypass safety guards | global |
-v, --verbose | Enable verbose output | global |
--repo-relay-only | Only publish nostr events to repository relays, not user or default relays | global |
--repo <REMOTE|NADDR|NOSTR-URL> | Target repository for repo-scoped operations. Accepts a configured nostr:// remote name, an naddr, or a nostr:// URL. Overrides nostr.repo, tracked-upstream, and remote-based auto-detection. Available at any command position: ngit --repo upstream send ngit issue --repo upstream create ngit issue create --repo upstream | global |
--json | Output one machine-readable JSON document on stdout | global; conflicts with -i, --interactive |
-h, --help | Print help (see a summary with '-h') | — |
-V, --version | Print version | — |
Details
ask a coordinator to run one workflow once (kind-9840 Manual Trigger)
A Manual Trigger is a one-shot authorization for exactly the workflow file identified by its content hash at the resolved commit, so it can replay a push or pull-request workflow that does not declare manual. It needs no standing Service Request.
<COMMIT-ISH> defaults to HEAD. An annotated tag is published as both the commit it peels to (first) and the tag object id, so a single #c query finds the run either way; ngit refuses to publish c values that do not all peel to the same commit.
--workflow is a path in the repository, and its SHA-256 is taken from the blob at the resolved commit — never from the working tree, whose line endings and clean/smudge filters can differ from the object the coordinator hashes.