Skip to content

docs(skill): spell out the patch refresh commands - #20

Merged
TB516 merged 1 commit into
mainfrom
docs/patch-refresh-commands
Nov 9, 2026
Merged

TB516 merged 1 commit into
mainfrom
docs/patch-refresh-commands

Conversation

@TB516

@TB516 TB516 commented Nov 9, 2026

Copy link
Copy Markdown
Owner

The update skill's "Refresh the patches" step said what to achieve but not how, so each bump's agent made up its own way to rebase and regenerate patches/.

It now gives the exact commands. Each patch file is applied with git apply (the files are plain git diff output, so git am rejects them) and committed under its file name. Those commits are rebased onto the new tag, and each one is written back out with git diff. Using the file names as commit messages keeps the numbers through the rebase, gaps like the retired 0004/0005 included. The step also says where the old and new tags come from and how to number a new patch.

Proof: I ran the documented commands with old = new = v0.1.7 (the pinned tag) in a fresh upstream clone, and git status showed patches/ byte-for-byte unchanged. A trial rebase onto the latest v0.1.8 nightly stopped on a conflict in 0001 as expected, with the file name kept as the commit subject.

@TB516
TB516 merged commit 7287c98 into main Nov 9, 2026
2 checks passed
@TB516
TB516 deleted the docs/patch-refresh-commands branch November 9, 2026 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant