upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDanConwayDev <DanConwayDev@protonmail.com>2024-02-23 17:21:21 +0000
committerDanConwayDev <DanConwayDev@protonmail.com>2024-02-23 17:21:21 +0000
commitd0875a3a50b4a5e8ab087f7495ea10150d2c0e4f (patch)
tree177054652967c4a03d56e94f9d1c80f081ee6ec1
parente406e44f32ea737bd9d0070acb7cf99ce1e1c33a (diff)
refactor: populate readme
with introduction, commands and how to contribute
-rw-r--r--README.md33
1 files changed, 33 insertions, 0 deletions
diff --git a/README.md b/README.md
index b9aacd7..ac29f33 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,36 @@
1# ngit 1# ngit
2 2
3cli for code collaboration over nostr 3cli for code collaboration over nostr
4
5It supports both:
6
7* patches over nostr similar to `git format-patch` and `git send-email` following the [nip34 daft spec](https://github.com/nostr-protocol/nips/pull/997)
8* branches similar to pull request model popularised by github
9
10so that users can decide to work with either model using the same nost events.
11
12the term 'proposals' is used to bridge the divide between 'patches and patch sets over email' and 'PRs'
13
14patches produced using other nip34 clients will work with the nip34 patch model but wont have branch support.
15
16
17### Commands
18
19run from the directory of the git repository:
20
21* `ngit init` signal you are this repo's maintainer accepting proposals via nostr
22* `ngit send` issue commits as a proposal
23
24* `ngit list` list proposals; checkout, apply or donwload selected
25
26and when on a proposal branch:
27
28* `ngit push` send proposal revision
29
30* `ngit pull` fetch and apply new proposal commits / revisions linked to branch
31
32## Contributions Welcome!
33
34use ngit to submit proposals!
35
36install the tool with `cargo install ngit`, use a prebuilt binary or build from source off the master branch. \ No newline at end of file