Skip to content

tui: Add patch save functionality with configurable directory.#1

Open
putnopvut wants to merge 1 commit into
igsilya:mainfrom
putnopvut:save_patches
Open

tui: Add patch save functionality with configurable directory.#1
putnopvut wants to merge 1 commit into
igsilya:mainfrom
putnopvut:save_patches

Conversation

@putnopvut

Copy link
Copy Markdown

Add the ability to save patches and series to disk using the "w" key. Single patches save as individual mbox files, while series are saved to a subdirectory containing all patches in the series.

Patch files are named using git format-patch style (e.g., 0001-Fix-bug.patch) based on the patch subject and number.

Users can configure where patches are saved using the git config value leadlight.patchDirectory. If set, patches save to that directory under the repository root (created automatically if needed). If not set, patches save to the current working directory.

Key bindings:

  • "w" in table view: save highlighted patch or series
  • "w" in patch view: save currently viewed patch

Saving the patch to disk provides a way for users to open the patch in their editor of choice and send email replies to patches using git send-email or their tool of choice.

Assisted-By: Claude Sonnet 4.5 noreply@anthropic.com

Add the ability to save patches and series to disk using the "w" key.
Single patches save as individual mbox files, while series are saved
to a subdirectory containing all patches in the series.

Patch files are named using git format-patch style (e.g.,
0001-Fix-bug.patch) based on the patch subject and number.

Users can configure where patches are saved using the git config value
leadlight.patchDirectory. If set, patches save to that directory under
the repository root (created automatically if needed). If not set,
patches save to the current working directory.

Key bindings:
- "w" in table view: save highlighted patch or series
- "w" in patch view: save currently viewed patch

Saving the patch to disk provides a way for users to open the patch in
their editor of choice and send email replies to patches using `git
send-email` or their tool of choice.

Assisted-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Signed-off-by: Mark Michelson <mmichels@redhat.com>
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