From 6af8f8a7ea26745bac6c458d18013f2950b0d8e9 Mon Sep 17 00:00:00 2001 From: Ivan Date: Mon, 20 Apr 2026 21:12:50 -0500 Subject: [PATCH] fix(docs): format --- CONTRIBUTING.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5da85f6..9d1cb5d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -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. \ No newline at end of file +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.