fix(docs): format

This commit is contained in:
Ivan
2026-04-20 21:12:50 -05:00
parent 7bfb4b3467
commit 6af8f8a7ea
+14 -14
View File
@@ -8,25 +8,25 @@ Patches are the preferred way to contribute. Create your changes locally, export
2. Stage and commit your work:
```bash
git add -A
git commit -m "Short description of the change"
```
```bash
git add -A
git commit -m "Short description of the change"
```
3. Export the commit(s) as a `.patch` file:
```bash
# Single most recent commit
git format-patch -1
```bash
# Single most recent commit
git format-patch -1
# Last N commits
git format-patch -N
# Last N commits
git format-patch -N
# All commits since a branch point
git format-patch main..HEAD
```
# All commits since a branch point
git format-patch main..HEAD
```
This produces one `.patch` file per commit (for example `0001-my-change.patch`).
This produces one `.patch` file per commit (for example `0001-my-change.patch`).
## Sending the patch
@@ -65,4 +65,4 @@ You must disclose AI usage in the patch message body (or commit message, if you
We prefer models that run locally or offline when that is practical for you.
Contributions must still be yours to justify and maintain. Do not submit bulk-generated changes you have not read, understood, and tested. We are not looking for unreviewed AI output or style-only churn from tools used without engineering/architectural judgment.
Contributions must still be yours to justify and maintain. Do not submit bulk-generated changes you have not read, understood, and tested. We are not looking for unreviewed AI output or style-only churn from tools used without engineering/architectural judgment.