ngit ci status
show CI results, with the trust context of every signer behind them
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 status [OPTIONS] [TARGET]Arguments and options
| Input | Description | Details |
|---|---|---|
<TARGET> | PR (#<prefix>, nevent, or event-id), commit-ish, or nothing for HEAD | — |
--require-ci-trust <LEVEL> | Exit non-zero unless the current result is a success whose weakest run meets this trust floor | values maintainer-directed, operationally-associated |
--offline | Skip the relay fetch and NIP-05 trust verification, reading CI from the local cache | — |
-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
show CI results, with the trust context of every signer behind them
<TARGET> is resolved in this order:
#<hex-prefix>is always a PR/event-id prefix- an nevent, note, or full 64-character event id is always an event id, and must name a cached PR or one of its revisions
- otherwise a commit-ish, resolved with git (an annotated tag is queried by both its tag object id and the commit it peels to)
- a bare short hex that is not a commit-ish falls back to a PR event-id prefix
- with no target, the HEAD commit
A PR reports only the runs for its latest revision; results for earlier revisions are never presented as current.
Trust context describes why a result may deserve attention. No known context is an absence of evidence, never a finding against the signer. The integrity marker is separate from trust: it is ngit's own check that it holds the commit and that the workflow file at that commit hashes to what the coordinator signed.