128 lines
3.5 KiB
Markdown
128 lines
3.5 KiB
Markdown
When contributing to another's project, it is common for the contribution to be
|
||
of many commits and involve a discussion with the project's maintainer. This is supported
|
||
via Radicle's patches.
|
||
|
||
Here we give a brief overview for using patches in our hypothetical car
|
||
scenario. It turns out instructions containing the power requirements were
|
||
missing from the project.
|
||
|
||
```
|
||
$ git checkout -b flux-capacitor-power
|
||
$ touch REQUIREMENTS
|
||
```
|
||
|
||
Here the instructions are added to the project's README for 1.21 gigawatts and
|
||
commit the changes to git.
|
||
|
||
```
|
||
$ git add REQUIREMENTS
|
||
$ git commit -v -m "Define power requirements"
|
||
[flux-capacitor-power 3e674d1] Define power requirements
|
||
1 file changed, 0 insertions(+), 0 deletions(-)
|
||
create mode 100644 REQUIREMENTS
|
||
```
|
||
|
||
Once the code is ready, we open (or create) a patch with our changes for the project.
|
||
|
||
```
|
||
$ rad patch open --message "define power requirements" --no-confirm
|
||
|
||
🌱 Creating patch for heartwood
|
||
|
||
✓ Pushing HEAD to storage...
|
||
✓ Analyzing remotes...
|
||
|
||
z6MknSLrJoTcukLrE435hVNQT4JUhbvWLX4kUzqkEStBU8Vi/master (f2de534) <- z6MknSL…StBU8Vi/flux-capacitor-power (3e674d1)
|
||
1 commit(s) ahead, 0 commit(s) behind
|
||
|
||
3e674d1 Define power requirements
|
||
|
||
|
||
╭─ define power requirements ───────
|
||
|
||
No description provided.
|
||
|
||
╰───────────────────────────────────
|
||
|
||
|
||
✓ Patch f504e78d71e7c2d70569976ef9f6b37b6a3d0bfd created 🌱
|
||
```
|
||
|
||
It will now be listed as one of the project's open patches.
|
||
|
||
```
|
||
$ rad patch
|
||
|
||
❲YOU PROPOSED❳
|
||
|
||
define power requirements f504e78d71e R0 3e674d1 (flux-capacitor-power) ahead 1, behind 0
|
||
└─ * opened by did:key:z6MknSLrJoTcukLrE435hVNQT4JUhbvWLX4kUzqkEStBU8Vi (you) [..]
|
||
└─ * patch id f504e78d71e7c2d70569976ef9f6b37b6a3d0bfd
|
||
|
||
❲OTHERS PROPOSED❳
|
||
|
||
Nothing to show.
|
||
|
||
$ rad patch show f504e78d71e7c2d70569976ef9f6b37b6a3d0bfd
|
||
|
||
patch f504e78d71e7c2d70569976ef9f6b37b6a3d0bfd
|
||
|
||
╭─ define power requirements ───────
|
||
|
||
No description provided.
|
||
|
||
╰───────────────────────────────────
|
||
|
||
commit 3e674d1a1df90807e934f9ae5da2591dd6848a33
|
||
Author: radicle <radicle@localhost>
|
||
Date: Thu Dec 15 17:28:04 2022 +0000
|
||
|
||
Define power requirements
|
||
|
||
diff --git a/REQUIREMENTS b/REQUIREMENTS
|
||
new file mode 100644
|
||
index 0000000..e69de29
|
||
|
||
```
|
||
|
||
Wait, lets add a README too! Just for fun.
|
||
|
||
```
|
||
$ touch README.md
|
||
$ git add README.md
|
||
$ git commit --message "Add README, just for the fun"
|
||
[flux-capacitor-power 27857ec] Add README, just for the fun
|
||
1 file changed, 0 insertions(+), 0 deletions(-)
|
||
create mode 100644 README.md
|
||
$ rad patch update --message "Add README, just for the fun" --no-confirm f504e78d71e7c2d70569976ef9f6b37b6a3d0bfd
|
||
|
||
🌱 Updating patch for heartwood
|
||
|
||
✓ Pushing HEAD to storage...
|
||
✓ Analyzing remotes...
|
||
|
||
f504e78d71e R0 (3e674d1) -> R1 (27857ec)
|
||
1 commit(s) ahead, 0 commit(s) behind
|
||
|
||
|
||
✓ Patch f504e78d71e7c2d70569976ef9f6b37b6a3d0bfd updated 🌱
|
||
|
||
```
|
||
|
||
And lets leave a quick comment for our team:
|
||
|
||
```
|
||
$ rad comment f504e78d71e7c2d70569976ef9f6b37b6a3d0bfd --message 'I cannot wait to get back to the 90s!'
|
||
84ef44764de73695cf30e6b284585d2c50d6d0e5
|
||
$ rad comment f504e78d71e7c2d70569976ef9f6b37b6a3d0bfd --message 'I cannot wait to get back to the 90s!' --reply-to 84ef44764de73695cf30e6b284585d2c50d6d0e5
|
||
2fa3ac18d82ebdafe73484a15fa9823355c4664b
|
||
```
|
||
|
||
Now, let's checkout the patch that we just created:
|
||
|
||
```
|
||
$ rad patch checkout f504e78d71e7c2d70569976ef9f6b37b6a3d0bfd
|
||
✓ Performing patch checkout...
|
||
✓ Switched to branch patch/f504e78d71e
|
||
```
|