{ "id": "826a6a8b5cd202072d7a652c0ae21577618ee167d2dc2f45b112f943cf9ce49b", "pubkey": "d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c", "created_at": 1714652324, "kind": 1621, "tags": [ [ "r", "26689f97810fc656c7134c76e2a37d33b2e40ce7" ], [ "a", "30617:a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d:ngit", "wss://relay.damus.io", "root" ], [ "p", "a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d" ] ], "content": "ngit clone\n\nI was thinking that a `ngit clone ....` command might be useful.\n\nUsage:\n\n```bash\n$ ngit clone NADDR|REPO_NAME\n```\nwhere `NADDR` is the naddr of the kind 30617 git announcement event and `REPO_NAME` can be:\n* just the repository name, and it would default to searching it on gitworkshop.dev\n* `@usename:repo` where username would be resolved using the logged in user's contact list (if there are no ambiguities)\n* `npub|nprofile|nip05:repo`\n\nThe command would call `git clone` using the first provided clone git repository, using others as fail-overs. It would also set non-primary clone repositories as other git remotes using `git remote add`.\n\nWhat do you all think? If you like it, I would like to take a shot at implementing it.\n", "sig": "3a692aa7ad9c9c81b29fe6f4160ba0548bf6d549f188850d11cb26fe3280273b0f6c121c469a234ff63a56dc3a8b63c86da043183568c2575b3fce48fa8b51ba" }