pull down to refresh

105 sats \ 2 replies \ @optimism 2 Apr \ parent \ on: Sign Git with your Nostr keys bitdevs nostr devs

I get to the wizard now!

But when I should input it already quit the script.

Is there a way to just manually configure?

╔══════════════════════════════════════════════╗
║  git-nostr-sign  ·  setup wizard             ║
╚══════════════════════════════════════════════╝

  This wizard will:
    1. Set publisher identity (import nsec, Amber, or new keypair)
    2. Deploy a NIP-05 address to Codeberg Pages (free)
    3. Configure your git to sign commits with your Nostr key

  Press Ctrl+C at any time to cancel.


─── Phase 1 · Tool Identity ─────────────────────

Publisher identity (NIP-05 + release metadata)
  1.  Import existing nsec or hex     — reuse a key you already have
  2.  Amber (NIP-46)                  — private key stays on your phone
  3.  Generate new dedicated keypair  — fresh “project” publisher key

Enter number: / # 1
/bin/sh: 1: not found
write
compose
10 sats \ 1 reply \ @optimism 2 Apr

Tested through npm run setup, which doesn't terminate on the menu when ran like that.

Findings from setup process:

  1. QR cannot be read by Amber when using a standard macos terminal font
  2. Amber through bunker doesn't seem to work - the app never talks to Amber, according to Amber (others do) I tried with multiple relays
  3. When going the new keypair route (option 3), I get the npub echo'd to me, but then after skipping step 2 (because codeberg is still centralized, so let's not) I am asked to type the nsec. This is odd, because I was never given it. When I enter nothing, it terminates.

You really, really, really need more testing.

reply
72 sats \ 0 replies \ @mf OP 3 Apr

That's true. Appreciate the feedback.

0.3.0:

➤ git-nostr-setup -h

git-nostr-setup / npm run init -- …  —  interactive wizard (default)

Non-interactive (--non-interactive or -N):

  Identity (pick one):
    --generate-identity           New random keypair (commits + updater)
    --identity-nsec <nsec|hex>   Existing key (also: GNS_IDENTITY_NSEC)
    --bunker-url <bunker://…>   Amber NIP-46 (approve on phone; GNS_BUNKER_URL)
    --reuse-identity              Keep identity.json, refresh signing + git only

  Signing override (optional — at most one):
    --signing-nsec …             Different local key for commits
    --signing-bunker-url …       Different Amber bunker for commits

  Git (pick one):
    --git-global                 Global gpg.program + signing
    --git-local                  This repo only (must be inside a git work tree)
    --no-git-config              Only write config.json / identity.json

    --no-pre-push-hook           Skip core.hooksPath .githooks

  Examples:
    git-nostr-setup -N --generate-identity --git-global
    git-nostr-setup -N --identity-nsec "$GNS_IDENTITY_NSEC" --git-global
    git-nostr-setup -N --bunker-url 'bunker://…' --git-local

  NIP-46 still needs Amber approval the first time. QR: set GNS_QR_SMALL=1 for a smaller pattern.
  Secrets in argv hit shell history — prefer env vars.
reply