Skip to content

Guides

Choose the task you want to complete. Each guide gives you the safe sequence, the important boundary, and a way to verify the result. When you need exact syntax, it links into the command tree generated from ngit's own CLI definitions:

Use this page to find the guide. Use the generated pages for exhaustive flags, defaults, conflicts, and accepted values.

Repositories

TaskGuideCLI reference
Publish a repositoryRepositoriesngit init
Inspect metadata and hostingRepositoriesngit repo
Edit metadata or providersRepositoriesngit repo edit
Accept, leave, or follow a rosterMaintainersngit repo
Synchronise Git serversRepositoriesngit sync

Pull requests and issues

TaskGuideCLI reference
Open a PR by pushing pr/*Pull requestsngit send for advanced input
List, view, review, or edit PRsPull requestsngit pr
Merge a PRPull requestsngit pr merge
Create or manage issuesIssuesngit issue

Releases, CI, and publication

TaskGuideCLI reference
Check for or install an ngit updateInstallngit update
Publish and verify software releasesReleasesngit release
Inspect or request CICIngit ci
Publish a static NIP-5A siteGenerated referencengit nsite
Publish an OCI imageGenerated referencengit container

Accounts and coding agents

TaskGuideCLI reference
Log in, create, select, or remove identitiesAccounts & keysngit account
Install or update the repository skillAgent automationngit skill

Automation rules

  • Add --json when the command supports machine-readable output. It writes one JSON document to stdout and keeps diagnostics on stderr.
  • After an initial online read has populated the cache, add --offline where the specific generated command page lists it.
  • Select ambiguous repositories with --repo <REMOTE|NADDR|NOSTR-URL>.
  • Prefer secret-file options over inline secret arguments in CI.

Do not infer that a global-looking flag works everywhere. The generated page for each command is the authority.

Git collaboration, without the platform.