patchy-cli 0.0.20 → 0.0.21-pr.227.6226056

package/README.md

@@ -1,6 +1,6 @@
 <p align="center">
   <a href="https://github.com/richardgill/patchy">
-    <img width="180" src="./assets/logo.png" alt="Patchy logo">
+    <img width="120" src="./assets/logo.png" alt="Patchy logo">
   </a>
 </p>
 <br/>
@@ -15,114 +15,43 @@
 
 A CLI for generating and applying patches to git repositories.
 
-## Patches vs forks
+## Why Patchy?
 
-A traditional fork means maintaining a separate repository or long-lived branch. Over time, your history diverges from upstream, which can make updates painful.
+For long-lived git forks with no plans to merge upstream:
 
-With patches, you store changes as `.diff` files alongside the upstream repo. You can inspect them, edit them, and apply them to a fresh clone of the repo.
+- A **git fork** stores your changes as commits.
+- **Patches** store them as `.diff`
 
-## What is Patchy?
+Patch files are a clean way to store long-lived changes - human-readable, easy to review and version. But managing them can be cumbersome.
 
-Patchy helps you **generate** and **apply** `.diff` patches for a git repo you've cloned on your machine.
+Patchy makes managing patches easy: make changes to a clone → save them as patches → reapply anytime.
 
-It's opinionated and has [conventions](#patch-file-layout) about how the `.diff` files are stored.
+## How it works
 
-## Example
-
-Starting a patch-based fork of https://github.com/octocat/spoon-knife.
-
-### Setup Patchy
-
-Create a folder for the fork: `mkdir spoon-knife-fork && cd spoon-knife-fork`
-
-- [Install Patchy](#installation)
-- Run `patchy init`
-  - press enter to select all the default options
-
-`patchy init` creates your config: `./patchy.json` ([full reference](#patchyjson-reference))
-```json5
-{
-  "source_repo": "https://github.com/octocat/spoon-knife",
-  "patches_dir": "./patches/",
-  "clones_dir": "./clones/",
-  "target_repo": "spoon-knife",
-  "base_revision": "d0dd1f61b33d64e29d8bc1372a94ef6a2fee76a9",
-  "upstream_branch": "main"
-}
-```
-
-`patchy init` also creates an empty `./patches` folder and clones the spoon-knife repo into `./clones`:
-
-```
-./
-├── patches/
-├── clones/
-│   └── spoon-knife/
-│       └── path/to/existingFile.txt
-└── patchy.json
-```
-
-### Make changes to the cloned repo
-
-We can now make changes directly in the cloned spoon-knife repo:
-
-```bash
-echo "edit existing file" >> clones/spoon-knife/path/to/existingFile.txt 
-echo "new file" > clones/spoon-knife/path/to/newFile.txt 
-```
-
-### Generate patches:
-
-To generate the patches for the changes run `patchy generate`:
-
-Patchy will prompt you to create your first **patch set**, let's name it: 'first-patch-set'
+`patchy init` sets up your project:
 
 ```
-./
+├── patchy.json              ← config (source: github.com/org/repo, base: v2.1.0)
 ├── clones/
-│   └── spoon-knife/
-│       ├── path/to/existingFile.txt
-│       └── path/to/newFile.txt
-├── patches/
-│   └── 001-first-patch-set/ (created)
-│       ├── path/to/existingFile.txt.diff (generated)
-│       └── path/to/newFile.txt (generated)
-└── patchy.json
+│   └── upstream-repo/       ← a clone of the source repo - your working copy
+└── patches/                 ← empty for now - your patches live here
 ```
 
-- **Edits** are stored as `.diff` files e.g. `existingFile.txt.diff`.
-- **New files** are copied as regular files e.g. `newFile.txt` (easier to inspect and edit directly). 
+The workflow:
 
-### Reapplying patches:
-
-Reset the current upstream repo with `patchy repo reset`, which will reset everything to `base_revision`:
+1. Make changes directly in `clones/upstream-repo/`
+2. Run `patchy generate` to generate patches:
 
 ```
-./
-├── clones/
-│   └── spoon-knife/  <<< reset
-│       ├── path/to/existingFile.txt
-├── patches/
-│   └── 001-first-patch-set/
-│       ├── path/to/existingFile.txt.diff
-│       └── path/to/newFile.txt
-└── patchy.json
+patches/
+└── 001-feature-name/
+    ├── src/file.ts.diff     ← edits to existing files
+    └── src/newFile.ts       ← new files (no .diff suffix)
 ```
 
-Apply the patches back to the cloned repo with: `patchy apply`
+3. Run `patchy apply` to reapply your patches to `clones/upstream-repo/` anytime
 
-```
-./
-├── clones/
-│   └── spoon-knife/
-│       ├── path/to/existingFile.txt (modified)
-│       └── path/to/newFile.txt (added)
-├── patches/
-│   └── 001-first-patch-set/
-│       ├── path/to/existingFile.txt.diff
-│       └── path/to/newFile.txt
-└── patchy.json
-```
+See the [example walkthrough](./docs/example.md) for a step-by-step guide.
 
 ## Getting started 
 
@@ -227,6 +156,8 @@ patches/
     └── patchy-post-apply  # runs after patches
 ```
 
+Patch sets support scripts without diffs, enabling pure automation steps.
+
 ### Hook execution
 
 - Hooks run with `cwd` set to `target_repo`
@@ -258,6 +189,8 @@ If `--patch-set` is not provided (and not set via env/config), prompts to select
 
 Note: `patchy generate` is destructive and will remove any unneeded files in the patch set directory.
 
+---
+
 ### `patchy apply`
 
 Apply patch files from `patches/` into `target_repo`. Patch sets are applied in alphabetical order.
@@ -270,7 +203,25 @@ patchy apply [--only <patch-set>] [--until <patch-set>] [--auto-commit=<mode>] [
 |------|-------------|
 | `--only <name>` | Apply only the specified patch set |
 | `--until <name>` | Apply patch sets up to and including the specified one |
-| `--auto-commit=<mode>` | Control auto-commit behavior: `all` (commit everything), `interactive` (prompt on last, default), `skip-last` (leave last uncommitted), `off` (commit nothing) |
+| `--auto-commit=<mode>` | Control auto-commit behavior (see below) |
+
+#### Auto-commit behavior
+
+Each patch set creates a single commit with message `Apply patch set: <name>`. The `--auto-commit` flag controls when commits happen:
+
+| Mode | Behavior |
+|------|----------|
+| `interactive` (default) | Commits all patch sets automatically, prompts for the last one |
+| `all` | Commits every patch set immediately after applying |
+| `skip-last` | Commits all except the last patch set |
+| `off` | No commits are made |
+
+**Notes:**
+- In non-interactive environments (e.g., CI), `interactive` mode auto-commits everything
+- Commits are skipped if any patch in the set fails to apply
+- `--dry-run` skips all commits
+
+---
 
 ### `patchy repo reset`
 
@@ -280,6 +231,8 @@ Hard reset the Git working tree of `target_repo` to `base_revision`. Discards al
 patchy repo reset [--base-revision] [--target-repo]
 ```
 
+---
+
 ### `patchy repo clone`
 
 Clone a repository into a subdirectory of `clones_dir` and checkout `base_revision`. The target directory is derived from the repo name.
@@ -288,6 +241,8 @@ Clone a repository into a subdirectory of `clones_dir` and checkout `base_revisi
 patchy repo clone [--source-repo] [--clones-dir] [--base-revision]
 ```
 
+---
+
 ### `patchy base [revision]`
 
 View or update the `base_revision` in config.
@@ -297,6 +252,8 @@ patchy base              # Interactive
 patchy base abc123def    # Set base_revision to the specified SHA or tag
 ```
 
+---
+
 ### `patchy prime`
 
 Prints a prompt you can include in your `AGENTS.md` / `CLAUDE.md`.
@@ -313,6 +270,8 @@ patchy prime >> CLAUDE.md
 
 Outputs a brief description of Patchy, key paths, and essential commands to help AI coding agents understand your project's patch workflow.
 
+---
+
 ### `patchy config get <key>`
 
 Output a single config value (raw, no label). Useful for shell scripts.
@@ -345,6 +304,8 @@ patchy config get verbose             # false
 - Unset raw keys exit with code 1
 - Unset computed keys (e.g., `patch_set_path` when `patch_set` is not set) output an empty line
 
+---
+
 ### `patchy config list`
 
 Output all config values as aligned key-value pairs.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchy-cli",
-  "version": "0.0.20",
+  "version": "0.0.21-pr.227.6226056",
   "description": "A CLI tool for managing Git patch workflows.",
   "type": "module",
   "bin": {
@@ -64,14 +64,13 @@
     "url": "https://github.com/richardgill/patchy"
   },
   "optionalDependencies": {
-    "patchy-cli-linux-x64": "0.0.20",
-    "patchy-cli-linux-arm64": "0.0.20",
-    "patchy-cli-darwin-x64": "0.0.20",
-    "patchy-cli-darwin-arm64": "0.0.20",
-    "patchy-cli-windows-x64": "0.0.20"
+    "patchy-cli-linux-x64": "0.0.21-pr.227.6226056",
+    "patchy-cli-linux-arm64": "0.0.21-pr.227.6226056",
+    "patchy-cli-darwin-x64": "0.0.21-pr.227.6226056",
+    "patchy-cli-darwin-arm64": "0.0.21-pr.227.6226056",
+    "patchy-cli-windows-x64": "0.0.21-pr.227.6226056"
   },
   "publishConfig": {
     "access": "public"
-  },
-  "packageManager": "bun@1.3.4"
+  }
 }