diff options
| -rw-r--r-- | README.md | 33 |
1 files changed, 33 insertions, 0 deletions
| @@ -1,3 +1,36 @@ | |||
| 1 | # ngit | 1 | # ngit |
| 2 | 2 | ||
| 3 | cli for code collaboration over nostr | 3 | cli for code collaboration over nostr |
| 4 | |||
| 5 | It 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 | |||
| 10 | so that users can decide to work with either model using the same nost events. | ||
| 11 | |||
| 12 | the term 'proposals' is used to bridge the divide between 'patches and patch sets over email' and 'PRs' | ||
| 13 | |||
| 14 | patches produced using other nip34 clients will work with the nip34 patch model but wont have branch support. | ||
| 15 | |||
| 16 | |||
| 17 | ### Commands | ||
| 18 | |||
| 19 | run 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 | |||
| 26 | and 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 | |||
| 34 | use ngit to submit proposals! | ||
| 35 | |||
| 36 | install the tool with `cargo install ngit`, use a prebuilt binary or build from source off the master branch. \ No newline at end of file | ||