Discover repositories from Nostr relays (NIP-34). Filter by pubkey or search term.

Get a single repository by ID or owner+name

Resolve repo by Nostr identity (npub or hex) and repo name. Returns cloneUrl (prefer git.gittr.space), cloneUrls, relays for location-agnostic use.

Full-text search across repository names and descriptions

Exact reverse lookup: given one or more forge URLs (GitHub, GitLab, Codeberg, Gitea, …) or github owner/repo shorthand, find Nostr kind-30617 announces with that source/forkedFrom. Returns npub + gittr URL so you can DM owners when the forge is unreachable. Does NOT fuzzy-match renamed slugs.

Alias for findReposBySource (exact forge URL → npub). Prefer findReposBySource for non-GitHub forges.

List repositories owned by the current user (from .nostr-keys.json)

Push files to the git server (REQUIRES signing with privkey). This replaces the branch with one new snapshot commit. It does not keep imported GitHub history. Optional deletedPaths removes files or whole folders on that snapshot (same as gittr UI folder delete); allowTreeShrink defaults true when deletes are present.

Publish repository to Nostr (kind 30617). Always writes the same clone addresses as the website Push (gittr, ngit, gitnostr, shakespeare, danconway). A GitHub URL is kept as the source, not as a clone. The private key is loaded from .nostr-keys.json when omitted.

Publish repository state to Nostr (kind 30618). HEAD follows branch when passed, otherwise main or master, not the alphabetically first branch. The private key is loaded from .nostr-keys.json when omitted.

CREATE A REPO IN ONE CALL - Push files AND publish to Nostr. Best for agents! Auto-loads credentials from .nostr-keys.json.

Show whether Nostr keys are loaded (hex/npub only — never returns private key). Use first in a session.

Create a disposable TEST Nostr keypair and write .nostr-keys.json so all tools auto-load it. ASK THE USER FIRST — a keypair is a permanent Nostr identity. Without confirm:true this only returns the question to ask. Never overwrites real credentials unless force:true.

Fork an existing repository

Same result as the website Push of a GitHub/GitLab repo. Copies the forge commits onto gittr (keeps history, updates an existing repo), announces the same git servers as the website, and publishes the branch tips with HEAD on the forge default branch. A second call keeps the existing name, description, and web links unless you pass new ones. Do not follow this with pushToBridge. If the forge returns 403 (account suspended or blocked), do not call this again and do not pass a different URL to change the source: this copies that URL onto the gittr bare repo and replaces every branch. Read the existing copy with bridgeListFiles after git ls-remote on https://git.gittr.space//.git. A new forge URL is not a way to leave a dead host: the owner uses the website sidebar If this git host is gone. See docs/AGENT-WORKFLOW.md.

Discover open bounties (issues with bounty labels or Lightning funding)

Get file content without a full local clone. Tries gittr bridge file-content, then a few hardcoded GRASP /raw/ hosts. Not full Code-tab parity (no 30617 clone[] / repo-files for home remotes) — prefer bridgeListFiles after importRemoteToBridge/mirrorRepo.

Add maintainer on kind 30617 (republishes full announcement with updated maintainers tag — matches gittr UI)

List issues the way the website Issues tab does. Nostr issues, plus GitHub or Codeberg/Gitea issues when the repo source says so. A forge issue and a Nostr issue stay separate rows. GitLab sources stay Nostr-only, same as the website.

Create an issue - REQUIRES signing

Comments on an issue, same as the website. A 64-character Nostr id returns Nostr comments. issue-N or a number needs ownerPubkey and repoId and returns the forge comments. Nothing is posted back to GitHub.

Publish a NIP-22 comment (kind 1111) on an issue. Optional replyTo for threaded replies. Does not create/modify bounty (9806) events.

Comments on a pull request, same as the website. A 64-character Nostr id returns Nostr comments. pr-N or a number needs ownerPubkey and repoId and returns the forge conversation. Nothing is posted back to GitHub.

Publish a NIP-22 comment (kind 1111) on a pull request. Optional replyTo for threaded replies.

List pull requests the way the website does. Nostr pull requests, plus GitHub or Codeberg/Gitea pull requests when the repo source says so. They stay separate rows.

Create a pull request - REQUIRES signing

Create PR via gittr CLI - full flow including git push (RECOMMENDED for PRs)

Get public key from private key

Load Nostr credentials from .nostr-keys.json (for debugging)

Submit work on a bounty (claim it with PR/evidence)

Star a repo (NIP-25 kind 7 on the latest kind 30617 event: tags e+k+p, content +). Requires a published repo announcement on relays.

Unstar a repo (NIP-25 kind 7 on the 30617 event with content "-"). Same tags as starRepo.

List repos a user starred (kind 7 with #k 30617 and #e pointing at 30617 events; latest reaction per repo wins)

Watch a repo (NIP-51 kind 10018 followed-repos list — publishes full a tag set, same as gittr Watch button)

Unwatch a repo (republish kind 10018 without this repo)

List repos from your latest kind 10018 followed-repos event on relays

Get trending/popular repositories

Get contributors to a repository

Get branches for a repository

Get commit history for a repository

Not supported for UI release notes. For Zapstore/NIP-82 announce use announceSoftwareFromForgeRelease. For git tags use listReleases + publishRepoState.

List git tags from the bridge (refs/tags/*), not Zapstore software releases and not the website Releases tab

Fetch a public forge Release (GitHub/Codeberg/GitLab) with announceable binaries (APK, AppImage, DMG, linux tar.gz, MSI/EXE, IPA). Omit tag for latest. Set hash:true to compute sha256 (slow; required before announce).

List all forge Releases + assets for a source URL (same as gittr Releases tab). No NIP-82 MIME gate. Distinct from listReleases (git tags).

Announce software to Zapstore/NIP-82 (kinds 32267/30063/3063) from a forge Release binary. Same as gittr Nostr Apps (latest tag) or Releases → Announce on Nostr (tag=). Never a tagless app. Copies images: from the forge zapstore.yaml onto kind 32267. Optional pinToBlossom uses public Blossom; blossom.gittr.space only for the official gittr APK (space.gittr.app). Auto-loads .nostr-keys.json if privkey omitted.

NIP-09 kind 5 deletion for previously published NIP-82 app/release/asset event ids (does not delete the git repo).

Owner soft-delete for a NIP-34 repo: publish replaceable 30617 with deleted markers + NIP-09 kind 5, and POST the signed 30617 to the bridge /api/nostr/repo/event (same as gittr Settings → Delete). Alias: deleteRepo.

Alias for softDeleteRepo — soft-delete a NIP-34 repository (owner only).

Low-level: publish NIP-82 events from an already-fetched forge payload (ok:true + hashed announceable binary). Prefer announceSoftwareFromForgeRelease.

Publish Nostr Pages (NIP-5A kind 35128): upload static files through gittr’s Blossom proxy (kind 24242), then sign the named-site manifest. Requires index.html. Pass files or fromBridge:true to read the git tree. Default Blossom is blossom.gittr.space (Pages only — never for app installers).

Scan a gittr bridge repo’s manifests (package.json, yarn.lock, go.mod, …) and query OSV via POST /api/security/audit. Same data as the gittr Dependencies tab. Does not require the website audit UI flag.

Explore repositories by category/topic

Publish NIP-34 PR update (kind 1619): new tip commit + clone URLs

Publish NIP-34 status (1630 open, 1631 merged/applied, 1632 closed, 1633 draft) for an issue, PR, or patch root event

Create Lightning invoice for bounty escrow (POST /api/bounty/create). Use GITTR_LNBITS_* env or pass lnbitsUrl + lnbitsAdminKey. Publish kind 9806 after pay via publishBountyToNostr.

Publish gittr bounty metadata event (kind 9806)

List kind 9806 bounty events linked to an issue id

One issue, the way the website opens it. A 64-character id is the Nostr issue. issue-N or a number needs ownerPubkey and repoId and reads the forge issue.

One pull request, the way the website opens it. A 64-character id is the Nostr pull request. pr-N or a number needs ownerPubkey and repoId and reads the forge pull request.

Convenience: publish status 1632 (closed) for an issue

Convenience: publish status 1630 (open) for an issue

Convenience: publish status 1631 (merged/applied) for a PR root event

Full merge: git clone/fetch with signed HTTPS auth, merge PR head, push to bridge, optional 30618+1631. Signer must be repo owner OR on latest kind 30617 merge_maintainers (if that tag exists) OR on maintainers when merge_maintainers is absent. Requires git on PATH. repoId optional if derivable from PR a-tag.

Copy a Git URL onto the bridge. With the owner key, an existing forge repo is updated to the forge commits (history kept). Does not publish the Nostr card — use mirrorRepo for the same result as the website Push. Do not use pushToBridge to sync a forge. If the URL returns 403, do not retry it and do not pass a different URL to change source: this force-updates the gittr branches to match the URL. Read the existing bare repo with bridgeListFiles instead. Leaving a dead forge is the website sidebar If this git host is gone, not this tool.

GET /api/nostr/repo/exists — check if repo exists on bridge

GET /api/nostr/repo/files — list files for branch

GET /api/nostr/repo/file-content — raw file from bridge

GET /api/nostr/repo/refs

GET /api/nostr/repo/commits

GET /api/nostr/repo/push-payment — push cost and whether payer has paid intent

POST push-payment action create_intent — invoice for pay-to-push (owner wallet keys in body)

POST /api/nostr/repo/push-policy-sync — upsert push paywall from signed kind 30617 (use announcement event JSON from publishRepoAnnouncement)

POST /api/bounty/release — pay bounty to recipient Lightning address

POST /api/bounty/create-withdraw — LNURL-withdraw for bounty flow

POST /api/bounty/claim-withdraw — claim withdraw to recipient